Parameter history
How the numbers moved.
The registry records what each value is today. This records what it was before, and what changed it. The official documentation shows current state and dashboards show live state. Neither remembers.
IssuanceAllocator
2 parameters movedThe second row the one above said would go here. First observed at Arbitrum One block 504192623 by the reconciler, which had been red on this parameter since the redirect activated; confirmed at block 504322516. getTargetAllocation now returns 96.584 GRT per block for the Rewards Manager against a total of 120.73. The activation block itself is not established: this records when it was seen, not when it happened.
The row the one above asked for. The redirect activated: getTargetAllocation returns 96.584 GRT per block for the Rewards Manager. First observed at Arbitrum One block 504192623, confirmed at 504322516. issuancePerBlock() still reads 120.73, which is why the old row was watching the wrong function: that is the manager's configured rate, not what reaches it.
GIP-0089
2 parameters movedApproved by Council on 2026-08-26, stated effective 2026-08-31. Approval is not activation: at Arbitrum One block 500226907 on 2026-08-31 the Issuance Allocator still allocates the whole 120.73 GRT per block to the Rewards Manager and zero to its other target. This row records the vote. A second row goes here when the contract changes, and not before.
A reduction of 24.146 GRT per block, approved but not yet observed on chain. issuancePerBlock() read 120.73 at block 500226907 on 2026-08-31. When it reads 96.584, add the row and say which block.
Graph Horizon
5 parameters movedThe protocol capability and the shipped behaviour changed at different times, which is why this parameter is recorded as disputed.
A fixed penalty had to deter deliberate misbehaviour, which made it disproportionate for an honest operator with a chain data fault.
Removed from the protocol entirely rather than set to zero. The tokenomics page had not caught up as of 2026-08-30.
Before Horizon a delegator could have only one active undelegation, so exiting several positions meant serialising the thawing period. The new ceiling is the one the two official pages disagree about.
A switch that exists and is off is a different thing from an impossibility, and enabling it is a governance decision rather than a rewrite.
The move to Arbitrum One
1 parameter movedRemoved the early-mover advantage and with it an entire genre of curation timing strategy. Exact activation date not established here; recorded as the L2 move.
GIP-0051
1 parameter movedThe size of that gap is the argument the GIP makes for the change. Exact activation date not established here; recorded as the GIP that made it.
What this is not
A partial record, and it says so.
This holds only changes somebody has recorded here with a source. The protocol has moved in ways this page does not yet cover, and two entries carry a year rather than a date because the exact activation was never established. Inventing a day would have made the page look more complete and be less true.