Consensus Mechanism
Orbinum runs Aura for block production and GRANDPA for finality, with a permissioned validator set today and Nominated Proof-of-Stake (NPoS) as the target model.
Aura and GRANDPA are live and work as described below. NPoS validator selection is not yet active: the current validator set is permissioned, with candidates approved by governance (no bond). Nomination and slashing arrive with NPoS.
See Staking & Rewards for the target model and the path to open validation.
Overview
Orbinum leverages Substrate's battle-tested NPoS consensus, which provides:
- 6-second block time via Aura (Authority Round)
- ~12-second finality via GRANDPA (GHOST-based Recursive Ancestor Deriving Prefix Agreement)
- Byzantine fault tolerance with support for up to 1/3 malicious validators
- Deterministic finality rather than probabilistic (unlike PoW chains)
For detailed information about how Aura and GRANDPA work, see the Substrate documentation on consensus.
Orbinum-Specific Configuration
Network Parameters
| Parameter | Value |
|---|---|
| Block Time | 6 seconds |
| Finality Time | ~12 seconds |
| Authority Set Size | TBD (testnet: ~50, mainnet: 100-300) |
| Session Duration | TBD |
| Unbonding Period | Expected 7-28 days |
Validator Economics
The economic incentives for validators are built into the ORB tokenomics. This includes block rewards from the 30% allocated for staking and transaction fee sharing.
For full details on token allocation, rewards, and the reward model, see:
Slashing Conditions:
- Double signing / Finality equivocation
- Extended unresponsiveness
- Invalid block production
For Validators
For detailed information on running a validator node, including hardware requirements, setup, monitoring, and key management, see:
Learn More
📄️ Consensus Mechanism
Orbinum's consensus - Substrate's NPoS with Aura and GRANDPA.
📄️ Node Operations
Running and maintaining Orbinum nodes in testnet environments.