SB Core
Overview
Consensus, execution model, and throughput
Consensus
SB Chain uses RDPoS (Randomized Delegated Proof of Stake) consensus — an evolution of standard DPoS that introduces randomisation into the witness selection and block production schedule.
Token holders vote for a set of active witnesses who are responsible for producing and signing blocks. The protocol reaches consensus when a supermajority of active witnesses have signed a block.
| Parameter | Value |
|---|---|
| Active witness set | Up to 1001 witnesses (governance configurable, default 21 active) |
| Block production | Randomised across the active witness set each round — not fixed or predictable in advance |
| Block signing | Each block signed by exactly one witness (witness_signature in block_header) |
| Missed slot | Skipped — no slashing, participation record updated |
| Randomisation | Reduces the ability of witnesses to coordinate timing-based attacks or censor specific transactions |
| Fault tolerance | Byzantine Fault Tolerant within the active witness set |
Execution
All exchange state — order books, account balances, open orders, price feeds, collateral positions — lives on-chain as part of the blockchain state. There is no off-chain matching engine and no external database.
- Every operation is included in a block and executed deterministically by all nodes
- Transaction ordering is determined by block inclusion — no mempool reordering after inclusion
- All state transitions are auditable and reproducible from genesis
Block Time & Throughput
| Metric | Value |
|---|---|
| Block time (mainnet) | 3 seconds |
| Minimum block interval | 1 second |
| Maximum block interval | 30 seconds |
| Default max block size | 2,000,000 bytes |
| Default max transaction size | 2,048 bytes |
| Theoretical max TPS (default config) | ~976 TPS at 1s blocks |