Juno v31 · validator status

Monitoring for v31 ended five hours after the halt at height 42,452,000: 7 October 2026, 13:56:31 CEST (11:56:31 UTC). This archived page makes no live RPC or staking-metadata requests. Its summary counts validators with saved participation evidence within that window, using voting power from the upgrade validator set. It does not show current signing or a consensus quorum. Later evidence is excluded from the result; the original archive remains available.

First participation evidence uses the earliest saved consensus vote or canonical block signature. The ≤ delay and “By” time are upper bounds: the validator was participating by then, but may have been ready earlier. Source labels distinguish pre-restart votes from block signatures; a first signature after restart does not by itself prove an upgrade after restart. A nil vote proves participation but is not agreement on a block. Vote times are reported by validators; capture times and coverage gaps remain in the archive. This measures observed consensus participation, not binary installation or an exact readiness ranking. For v31 only the recovered 09:32 Berlin snapshot survives; absence there is not proof of being unready.

First-signature delay uses each validator’s first included precommit timestamp after the upgrade halt. It includes the shared network halt. The block offset shows how many blocks after the first resumed block it appeared. These observations cannot reconstruct earlier readiness or actual software-upgrade duration; validator clocks and commit inclusion can differ.

A missing block signature may be a missed block or a signature not included in the commit; it does not establish a failed upgrade. Nil votes do not count as block signatures. Observations are RPC reports, not an independent cryptographic or software-version audit.

CometBFT canonical commits ↗