Skip to documentation

Economics

Emissions

Emission scheduling, the Minter deployment at TGE, lock rebase.

Emission schedule

Arc Mainnet's Minter is deployed at TGE. Until then no emissions accrue; this pre-emission period is Epoch 0. Epoch 1, the first emission epoch, begins at the first Thursday 00:00 UTC boundary after Minter deployment. The exact date is TBD.

updatePeriod becomes eligible at each epoch boundary; it does not run automatically. The weekly field starts at 10,000,000 ARCHERY per emission update, grows by 3% while epochCount is below 15, then decays by 1% before tail emissions.

When the weekly amount falls below the 8,969,150 ARCHERY tail threshold, emissions are computed from total supply and tailEmissionRate. The initial tail rate is 67 basis points. These are contract parameters, not an APR forecast.

Arc Testnet's Minter is deployed with one-hour epochs and five-minute voting boundaries, so its amounts and epoch counts are not a Mainnet preview.

Lock rebase

rebaseRateBps scales raw lock growth; it is configured at Minter kickoff and is not a guaranteed return. No emission or rebase occurs on a network until its Minter is deployed.

Rebase tokens flow to Rewards Distributor and gauge emission tokens to Voter. Ordinary ARCHERY wallet balances do not automatically rebase.

Distribution to gauges

Voter accounts for emissions using recorded pool weights and gauge indices. A successful period update does not mean every gauge or account has already received a claim. Follow the distribution and claim transactions to determine actual rewards.