Skip to Explorer content
All networksNetwork progress and wallet capabilities are compared across DevNet, TestNet and Mainnet. Searches remain scoped to TestNet.Times shown in UTC.

All networks · Chain progress

Network overview

Compare published heights and follow the evidence behind each checkpoint.

Checks every 30 seconds while this page is visible. Each network has its own height sequence.

DevNet

Not reported
Published checkpoint

Height not reported

A public DevNet height feed is not connected to Explorer yet.

Live chain tip
Not reported
Latest published finalization
Not reported
Source last checked successfully
Not yet available

TestNet

Checking source
Published checkpoint

Checking…

Reading the current TestNet publication.

Reading TestNet checkpoint
Live chain tip
Not reported
Latest published finalization
Not reported
Source last checked successfully
Not yet available

Mainnet

In development
Published checkpoint

Not launched

Mainnet heights will appear when its public chain feed becomes available.

Live chain tip
Not launched
Latest published finalization
Not reported
Source last checked successfully
Not yet available

TestNet · Published certificates

Recent checkpoints

Newest heights first. Open a height to inspect its validator certificate.

Loading published checkpoints
How to read these heights

A height identifies a position within one network’s chain. A larger DevNet or TestNet height does not mean that network is faster, safer or closer to launch.

TestNet currently publishes non-value internal-unit certificates through a Core-verified snapshot. Its published finality is separate from MPC signing and external-chain settlement. The certificate links expose the underlying evidence.

“Not reported” means no public height source is connected. “Source unavailable” means an existing source could not be read. Neither means height zero. Mainnet remains in development.

ALL NETWORKS · WALLET CAPABILITY COMPARISON

Wallet capabilities & readiness

A customer ceremony belongs to exactly one network, one authorization plane, one address namespace, and one evidence history. Availability is published only after every required gate passes.

DevNet, TestNet and Mainnet are shown together, regardless of the network selected above. Each network retains its own authority and evidence.

Loading wallet-network capabilities…

PROMOTION IS A CEREMONY

Software can advance. Authority cannot leak.

DEVNETEngineering proof

Fast iteration, valueless activation, and reproducible failure paths.

TESTNETRelease proof

Independent roots and operator evidence before release-candidate wallets exist.

MAINNETProduction authority

Separate governance, signer admission, operational acceptance, and value policy.

A network label is never sufficient authorization.PROFILE + ROOTS + PROTOCOL + ACCEPTANCE
HYBRID-CHAIN · NETWORK-SCOPED MPC AUTHORITY

Devnet, testnet, and mainnet never inherit enrollment authority, wallet keys, address namespaces, or ceremony evidence from one another.