Color Legend
Default: Implemented
Green: Implemented, but not merged yet
Blue: Needs to be implemented
Red: Deprecated
The rewards issuance is not enabled by default at the chain genesis. After the genesis block, several things need to happen before authoring blocks by anyone, and rewards can be enabled (TODO link to Genesis write-up). Then:
solution_range_for_rewards (TODO link to conversion write-up).initial_solution_range.initial_solution_range at the next erasolution_range_for_rewards below which to automatically enable rewards.solution_range_for_rewards at a certain block $B$.RewardsEnabled runtime item is set to true. The rewards will start to be paid to voters and proposer of the very next block.The issuance function currently consists of two components: a decaying component and a utilization-based component. The decaying component issues a constant reward for some initial interval and gradually reduces it over time. The utilization-based component issues a reward based on the average utilization of blockspace in recent blocks. Such construction allows for more decaying components to be included for additional incentivization.
Full Block
MAX_NORMAL_BLOCK_LENGTH is the byte size limit of a full block set to consensus and equal to 0.75*MAX_BLOCK_LENGTH (currently 3.75 MiB for) normal txs (different from operational (e.g., votes, equivocation) and mandatory (e.g., new archived segments))