all learn

Emission schedules: why coins halve, decay, or never stop

The block reward is a coin's printing press, and the schedule is its blueprint. The four design choices every schedule makes, the halving math on paper, and the blocks-vs-days trap hiding in every "per year" claim.

2026-10-16·updated 2026-10-16·5 min·pow.family research#tokenomics#beginner
01

Why schedules taper at all

Why not pay 100 coins per block forever? Two forces pull against flat emission. Scarcity: never-slowing supply dilutes holders forever and kills the "last coin mined" story that anchors store-of-value arguments. Bootstrap economics: young networks need generous rewards to attract hashrate before the coin is worth much — pay generously when security is hardest to buy, taper when it isn't.

And one force pulls back: the block reward *is* the security budget — the income paying miners to defend the chain. Taper to zero and eventually someone must pay for security another way (transaction fees, hopefully). Scarcity versus security is the tension every schedule resolves in its own shape.

02

Four design choices, five shapes

ChoiceOptions
Step size÷2 (halving) · ÷√2 · continuous decay curve
Step frequencyper era (years) · yearly · every block
Endpointzero · small perpetual tail · flat forever
Caphard cap · asymptote · none

Bitcoin picked ÷2 every four years to zero with a hard cap. Filling the grid differently gives the other familiar shapes: smooth decay to a cap (no halving day, ever), halvings plus a perpetual tail (the Dogecoin model), decay landing on a small tail, or many small steps — yearly staircases — instead of rare big ones. Each shape sets the coin's psychology as much as its math: dated tradeable events, or their deliberate absence.

03

Halvings, worked on paper

Take a generic coin: 100 coins per block, halving every 100,000 blocks, one block per minute. Era one pays 100 × 100,000 = 10,000,000 coins in ~69 days. Era two pays 5,000,000, era three 2,500,000, and the whole geometric series converges on 40 million — first era × 2, always. Each halving cuts miner income overnight by half and future dilution by half too; the day it lands is the one date on everyone's calendar.

04

Blocks, not days

Every schedule is denominated per *block*; what you feel is per *day*, and the conversion runs through block time: daily emission = reward × 86,400 ÷ block-time-seconds. A "60-second" chain running 80-second blocks emits 25% less per day than its docs imply — same schedule, different reality. Likewise a "yearly" halving defined as 525,600 blocks is a calendar year only at exactly 60-second blocks. Whenever you see a daily emission or a halving date, check whether the writer divided by the target block time or the measured one.

05

See it live on pow.family

The tracked set covers every shape in this lesson — halvings+tail, smooth decay to cap, decay to small tail, yearly staircases. Each project page states its constants under Tokenomics, and the Supply card shows issued supply against the cap or current era.

Sources

Related
More explainers
updated 2026-10-19ASIC vs GPU vs CPU: three ways to hashupdated 2026-10-19Bitcoin block rewards: subsidy, fees, and the coinbase transactionupdated 2026-10-16Merged mining (AuxPoW): one electric bill, two coinsupdated 2026-10-19The mining budget checklist: the true cost of a rigupdated 2026-10-19Electricity costs: the kWh math that dominates miningupdated 2026-10-19The mining glossary: every dashboard word, definedupdated 2026-10-16Pool mining vs solo mining: the variance tradeupdated 2026-10-16What is mining? The hash lottery and the block rewardupdated 2026-10-19Algorithm compatibility: hardware must match the puzzleupdated 2026-10-19Bitcoin difficulty: the 2,016-block thermostatupdated 2026-10-19Home installation: prep and the safety checklistupdated 2026-10-16How pools work: shares, the payroll ledgerupdated 2026-10-16Mining algorithms: SHA-256, Scrypt, RandomX — and why hardware differsupdated 2026-10-19Reading electricity tariffs: energy, demand, and fixed feesupdated 2026-10-16Tail emission and dilution: caps vs forever-moneyupdated 2026-10-19Airflow and temperature: the intake-exhaust loopupdated 2026-10-16Auditing supply claims: three formulasupdated 2026-10-19Halving planning: model subsidy cuts without the folkloreupdated 2026-10-16Mining difficulty: the network's thermostatupdated 2026-10-16Effort and luck: reading a pool roundupdated 2026-10-19Reading miner specifications (and their units)updated 2026-10-19Stratum: how your miner talks to a poolupdated 2026-10-19Time-of-use rates: scheduling mining around the clockupdated 2026-10-19Miner vs node: who actually enforces the rulesupdated 2026-10-19Your first miner: the go/no-go checklistupdated 2026-10-19Demand charges: you're billed on your peak, not just your kWhupdated 2026-10-19Monitoring baselines and safe restartsupdated 2026-10-16PPS, PROP, PPLNS: how pools payupdated 2026-10-16Hashrate: what those TH/s numbers actually meanupdated 2026-10-19Confirmations: why 'confirmed' is a probability, not a switchupdated 2026-10-19Mine or buy? The honest comparisonupdated 2026-10-19Miner efficiency: the J/TH that decides who survivesupdated 2026-10-19Securing the operation: management access and payout custodyupdated 2026-10-16Stale shares and latency: why ping barely mattersupdated 2026-10-19Buying used miners: inspection and seller checksupdated 2026-10-19Payout address safety: the one typo that costs everythingupdated 2026-10-19Measure your miner's real power drawupdated 2026-10-19Reading profit estimates, sensitivity, and payback honestlyupdated 2026-10-19Reconciling pool payouts: expected vs actually paidupdated 2026-10-19Network difficulty vs share difficultyupdated 2026-10-19Rejected shares: the troubleshooting ladderupdated 2026-10-19Site electrical review: before you add loadupdated 2026-10-16Choosing a pool: the actual checklistupdated 2026-10-19Cooling and heat: every watt becomes heatupdated 2026-10-19Uptime, availability, and reconciling the energy model
Emission schedules: why coins halve, decay, or never stop · pow.family