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

Governance of the consortium.

Administrative power over the control plane is held by a multisig of the validator entities. Nothing changes – anchor writers, registries, rule sets, admin rights – without a proposal confirmed on chain by three of the four. Every proposal, every confirmation and every execution is public below.

Like a board that must vote before anything is changed: here the votes are signatures, counted by the network itself.

Signatories and threshold

One key per entity. On the testnet the keys are derived from the operator’s seed; in production each entity holds its key in its own HSM or signing service. A fifth, independent signatory (academic or legal) is foreseen – the contract supports adding owners by proposal.

—signatures required of every proposal · mirrors the QBFT quorum

Proposal log

Newest first. A proposal is executed only after the threshold is reached; the executing transaction and its block are the proof.

#TitleTargetActionConfirmationsStatusExecuted

What the multisig controls

Policy rule sets

Versions of the deterministic decision rules of the control plane (identity, registration, volume, supervision). Each version is a hashed bundle with the block from which it applies – any past decision can be replayed against the rules then in force.

Reconnecting to the network…