Devnet, testnet and mainnet
You are looking at an old version of this page: revision #84 by zoobc.how, 2026-10-26 20:39 UTC. See the current version
ZooBC runs three networks: devnet, testnet and mainnet. Each is a separate chain with its own genesis block, its own nodes and its own balances. Mainnet is the network whose ZBC carry real value. Testnet works the same way with coins that have none, and devnet runs shorter timings for development.
Three separate chains
| mainnet | testnet | devnet | |
|---|---|---|---|
| chain id in its configuration | zoobc-mainnet | zoobc-test | zoobc-dev |
| purpose | real value | trying every feature without risk | developing and testing changes |
| rules and values | the reference | the same as mainnet | the same rules, shorter timings |
| genesis seats | 11 | 11 | 11 |
| genesis coins | 14 | the same 14 | the same 14 |
Because they are separate chains, the three networks share nothing:
- An address funded on one network has nothing on another: the API there reports a zero balance, not an error.
- A transaction signed for one network is invalid on the others, because every signature covers the genesis hash of the chain it was made for (chain-bound signatures).
- Nodes of different networks refuse to connect: they compare genesis hashes first (genesis block).
To check which network a node serves, read genesis_hash at /api/v1/node/info.
Mainnet
Mainnet is the network meant to carry real value. The values given across this wiki are mainnet's.
Testnet
Testnet is the public test network. From version 0.5.8 it mirrors mainnet: the same rules and the same values, such as 30-day snapshot cycles, an admission pace of 600 days divided by the seats (kept between 7 and 90 days, with the first newcomer 7 days after genesis), and a queue minimum of 100 ZBC with a ceiling of 250 ZBC (admission pace, registering a node). What works on testnet works the same way on mainnet.
Its coins carry no value. Anyone can claim some from the faucet on the testnet gateway, to try the wallet, tokens, markets, apps or the API. The faucet pays up to 100 ZBC on the first request, then 50, 25, 12.5 and so on, halving each time until a request would pay less than 1 ZBC. It counts what was drawn per address or per internet address, and the allowance resets weekly (gateways).
Devnet
Devnet is the development network, used to try changes. It keeps the 15-second block but shortens many durations, so that their effects show up within minutes or hours instead of days or weeks:
| devnet | mainnet and testnet | |
|---|---|---|
| rollback limit | 60 blocks (15 minutes) | 720 blocks (3 hours) |
| spine block | every hour | every day |
| depth of spine checkpoints and snapshots | 80 blocks | 760 blocks |
| snapshot cycle | 240 blocks (1 hour) | 172,800 blocks (30 days) |
| account rent | 1 ZBC per 240 blocks | 0.01 ZBC per 172,800 blocks |
| default update delay | 120 blocks | 11,520 blocks (2 days) |
| smallest unit of the score clock | 120 blocks (30 minutes) | 2,880 blocks (12 hours) |
| admission pace | 180 s ÷ seats, kept between 60 and 300 s | 600 days ÷ seats, kept between 7 and 90 days |
| queue minimum at launch | 1 ZBC (ceiling 2.5 ZBC) | 100 ZBC (ceiling 250 ZBC) |
Other mainnet parameters are listed in node parameters on mainnet.