Blockchain Genesis 2.0 testnetRunning testnet with a test import – not a production service, not audited, not approved by any regulator. A technical record, not a securities register.
Genesis Explorer
Transaction detail
—block —signatures on the latest block protocol finality —blocks verified last audit anchor— observer in sync

Operational status.

How the validators and the observer are doing, measured from the chain itself, and a public record of every incident.

Validator availability

Fulfilled slots: the share of a validator’s own proposal turns that produced a block. A missed turn triggers a QBFT round change and the next validator proposes; finality is never affected. Signatures count the seals recorded by the observer.

ValidatorData centreSlots · 24 hSlots · 7 dSlots · 30 dSigned · 24 hLast seenStatus

Block production

Blocks with transactions follow every 5 s, empty blocks every 60 s. Intervals above 60 s are round changes. There are no reorganisations by design.

Interval between consecutive blocks

Observer and explorer

The public layer reads only from the observer node. If the observer falls behind, the integrity line at the top says so; the validators continue regardless.

External anchoring

A second, independent timestamp makes a silent rewrite of history detectable. Each daily snapshot digest is timestamped in Bitcoin through OpenTimestamps (free public calendars) and – once the dedicated address is funded – recorded on Base, an Ethereum layer 2. Other anchoring targets (such as EBSI) are only being considered; no onboarding, integration or partnership exists. A timestamp proves existence at a time, not the truth or legal effect of the content.

A second, outside timestamp: the same fingerprint is also stamped into Bitcoin, which nobody here controls.

SnapshotBitcoin (OpenTimestamps)Base

Backups and recovery

The chain itself lives on five nodes. What only the observer holds – daily snapshots with their Merkle leaves, deployment and registry metadata, the incident log – is archived daily; the archive hash is anchored, and a recovery test reads the archive back and recomputes every Merkle root before its result is anchored too.

ArchiveSizeSHA-256AnchoredRecovery testOff-site copy

Incident log

Every disruption of the network or of this explorer, with cause, impact and fix. Entries are never removed.

Reconnecting to the network…