Network
How Inazuma reaches finality in under a second
A compact validator set, fast block propagation and a lean native runtime. Nothing exotic — just tuned for latency instead of theory.
- Block time
- 400ms
- Finality
- 1 block
- Nodes shown
- 26
Validator set
The mesh, live
Drag to rotate, scroll to zoom, hover a node for its status.
01
Consensus
A BFT-style consensus with deterministic finality. Once a block is confirmed it never reorgs, so exchanges and apps can treat one confirmation as final.
02
Validators
A staked validator set proposes and votes on blocks in rotation. Validators run modest hardware, keeping participation open as the set grows.
03
Execution
A purpose-built execution layer sits on top of consensus. Transfers, staking and native tokens are protocol operations, hashed into every state root.
Architecture
Block lifecycle
Step through the path a transaction takes — pick a stage.
Signed locally, broadcast to the nearest node over the encrypted transport. Nothing leaves the wallet unsigned.
Average end-to-end: 400ms block interval · sub-second confirmation
Roadmap
From devnet to decentralization
Phase 01
Devnet
Single-validator devnet with public RPC, explorer and faucet. Used to stress-test the chain before testnet.
Phase 02
Public testnet
Permissioned validator set, public RPC, explorer and faucet online.
Phase 03
Validator expansion
Multi-validator set, staking contracts and slashing rules.
Phase 04
Mainnet
Genesis distribution, canonical bridge and audited core contracts.
Phase 05
Decentralization
Permissionless validation and on-chain governance of protocol params.