Fifty a block, halving every 210,000 blocks, capped at 21,000,000

These are Bitcoin's issuance rules, copied deliberately. The cap matches so that supply is not one of the differences between the two chains, and the interval between halvingsThe permanent halving of the block reward, every 210,000 blocks, exactly as on Bitcoin. matches for the same reason.

Cap
21,000,000 WHAT Total supply, reached asymptotically. Cumulative issuance is 21,000,000 × (1 − 2⁻ʰ) after h halvings.
Opening reward
50 WHAT Per accepted block, minted to the address committed inside the header.
Halving interval
210,000 blocks Counted by height, not by the clock. Exactly Bitcoin's interval.

whitepaper §6

The schedule counts blocks, so hashpower cannot move it

The reward steps down every 210,000 blocks, and a block is a block whether it took four minutes or four hours to find. How much hashpower is present changes nothing about how many coins a block mints.

So a flood cannot compress the curve and an exodus cannot stretch it. What hashpower does change is the rate at which the chain walks along the schedule, and the difficulty rule holds that rate near ten minutes in both directions. The rule controls the block rate rather than the block count and keeps no memory of cumulative error, so the pace drifts a few per cent either way and the schedule itself does not move.

That bounds how fast coins come out. It says nothing about who receives them, which is settled block by block by whoever is hashing. See what a large arrival actually gets.

Fig. 7 — Issuance in coins. Block height across the bottom. Up the side, the reward per block and cumulative issuance, which is 21,000,000 × (1 − 2⁻ʰ) after h halvings. Halving boundaries are marked by height; there are no years on this chart. The marked point is where a block stops being worth submitting, because the fee to send one stays flat while the reward keeps halving — the end of issuance. Denominated in WHAT; there is no currency axis here.

whitepaper §5

And none of it can be edited

The schedule is not policy. It is arithmetic inside a script that has no upgrade path, which puts it beyond us, beyond a majority of hashpower and beyond any governance process — there is not one. See how to check the rules cannot change.