rounds, halvings and settlement
How a round opens and closes, how the reward halves, how a share is calculated, and how long you have to collect it.
the clock, not the solution
A round closes once its configured number of seconds has elapsed. More miners do not make rounds arrive faster, and an idle token does not stall: the next boundary is advanced from the previous scheduled boundary rather than reset to the current time, so a token nobody touched for an hour catches up one round per crank instead of losing its schedule. §3.1
Closing a round is a permissionless instruction that anyone can call, and calling it when nothing is due does nothing. It advances exactly one round per call, deliberately: a loop that caught up an idle token would be bounded only by elapsed time and would run out of compute. §3.6
the emission schedule
The reward for a round is the initial reward halved once per completed halving interval. It is computed from the round index every time it is needed rather than stored, so there is no cached figure that can drift if a boundary is ever missed. §3.3
- halvings
- (round_index - 1) / halving_rounds
- reward
- initial_round_reward >> halvings
- reward after 64 halvings
- 0
- budget for a round
- min(reward, unmined supply)
A schedule whose lifetime emission cannot release the full mineable allocation is rejected at launch, so no token can be created that would strand supply in its vault forever. §3.4
The public preset on this site is a 3,000,000 token supply with a 5% creator allocation, leaving 2,850,000 mineable across 60-second rounds, halving every 96,480 rounds from an opening reward of 14.769908 tokens. One base unit less per round is not enough to release the allocation and fails launch.
settlement
A round's budget is fixed at the moment it closes, computed against its own index so a halving on the boundary cannot shrink work already done, and clamped to what the vault still holds so settlement can never promise more than exists. §3.5
Each miner's share is the budget times their credited weight divided by the round's total weight, computed through a 128-bit intermediate and truncated. The truncation always favours the vault: integer shares can only sum to less than the budget, never more. The remainder stays unmined rather than being redistributed, because rounding up or handing out dust is exactly the path that overdraws a vault. §4.4
you have about half an hour to settle
A round's total weight only exists once the round closes, so a share is settled on the miner's next action rather than at submission. Closed rounds are kept in a fixed ring of 32 slots inside the token's config account.
- retained rounds
- 32
- at 60-second rounds
- about 32 minutes
- settled by
- mine, claim, deposit or withdraw
A slot resolves only when the round number stored in it matches the round being asked for, so a round that has been overwritten stops resolving rather than returning a newer round's numbers. Holding history this way costs no extra accounts and no extra rent, at any age and any number of miners. §4.5
A miner who acts every round always settles. A miner who walks away for longer than the ring forfeits the unsettled tail: that share is not lost to anyone else, it simply is never credited and the tokens stay in the vault.
empty rounds
If nobody submits during a round, its budget is never reserved. The round is recorded as an empty tombstone, the counter of empty rounds increases, and the schedule continues from the next index. Emission for that interval is not carried forward. §3.7
this page expands
- 3.1A round is a wall-clock interval, not a race to a solution
- 3.3Emission halves on a fixed interval and is never stored
- 3.5A round's budget is frozen when the round closes, and capped by the vault
- 4.4Settlement is pro-rata and truncates toward the vault
- 4.5Settlement history is a bounded ring of 32 rounds
The paper is the authority. Where this page and §3.1 disagree, the paper is right and this page is a bug.