Validator vs Candidate Rewards
Both pools are minted from the same base rate, but they are scaled differently. The validator pool is minted at the full base rate and does not shrink when fewer validators are qualified; the candidate pool is scaled by how many candidate seats are actually filled, so empty seats mean less candidate-side issuance.
| Item |
Validator Pool |
Candidate Pool |
| Minting rate |
Full base rate, independent of how many validators are qualified |
Base rate scaled by qualified seats over the candidate economic denominator |
| Allocation |
Distributed to active validators |
Split equally per qualified candidate seat, so each qualified seat receives the same share |
| Claim cadence |
Settled through the validator settlement path |
One claim per seat per claim period (86,400 economic seconds) |
| Stake requirement |
At least 100,000 MSG in steady state |
Between 10,000 and 100,000 MSG, with a 14-day unbonding period |
Two consequences follow from the scaling rule. First, a qualified candidate seat receives the same per-seat share whether few or many candidates are qualified, because both the inflow and the split use the qualified-seat count. Second, the candidate pool as a whole only reaches its full size when every candidate seat is filled, which is what the candidate economic denominator expresses. During the bootstrap admission window, the validator minimum-stake requirement is 0 at the genesis parameter; the 100,000 MSG figure above is the steady-state value restored once the active set crosses the threshold.