Changes to “Node parameters on mainnet”
#50 (zoobc.how, 2026-10-26 20:39 UTC) → #1075 (zoobc.how, 2026-10-27 00:42 UTC): Seed article updated
…
| Proof-of-ownership age | at most 720 blocks (3 hours) | How recent the block named in a proof of ownership must be |
| Queue order | stake × blocks waited | Ties go to the earlier registration height, then the lower node id |
+ | Attendance window | 5,760 blocks (1 day) | A queued node must show a sign of life once per window; failing any other sign it sends a QueueAttendance, whose fee comes out of the stake and goes to the longevity pool |
+ | Allowed missed windows | 90 | Over the whole wait, one admission cycle's worth: max(2, maximum delay ÷ 1 day); the 91st miss drops the node, and 90 % of its stake comes back at once |
− | Attendance window | 5,760 blocks (1 day) | A queued node must show a sign of life once per window |
− | Allowed missed windows | 90 | One admission cycle's worth: max(2, maximum delay ÷ 1 day) |
## Admission pace
…
| Parameter | Mainnet value | What it means |
|---|---|---|
+ | Exit cool-down | 40,320 blocks (7 days) | Time between a removal, or the owner's own claim, and the automatic return of the stake |
+ | Stake at risk | 10 % | Lost on expulsion (the other 90 % comes back at once), an exit while missing or suspended, leaving the queue or a queue drop; it goes to the longevity pool |
+ | Claim delay | 40,320 blocks (7 days) | A claim from any account but the owner's executes after this, unless the owner removes the node first |
− | Exit cool-down | 40,320 blocks (7 days) | Time between a removal and the automatic return of the stake |
− | Stake at risk | 10 % | Lost on expulsion, an exit while missing or suspended, leaving the queue or a queue drop; it goes to the longevity pool |
− | Claim delay | 40,320 blocks (7 days) | A claim by anyone but the owner executes after this, unless the owner removes the node first |
| Key rotation | 120 blocks (30 minutes) | Delay before a new node key takes effect |
…
| Production attempt | every 10 seconds | How often a registered node tries to produce; its selection thread runs every second |
| `auto_resync` | on | A wedged node rebuilds itself from the spine-anchored snapshots |
+ | Storage | on | Holding file pieces and archive chunks is a duty of the seat; an operator who switches it off only loses the storage rewards |
| Snapshot interval | 172,800 blocks (30 days) | How often every node writes a snapshot of the state |
| Blocks kept | 30 to 60 days | One to two snapshot periods; older blocks are pruned unless `keep_all_history` is set |
…