Emissions

Emission schedule

Minter deployment is deferred to a future reviewed deployment; this release has no kickoff phase. After a Minter is deployed and wired, updatePeriod becomes eligible at the next epoch boundary; it does not run automatically. Epoch duration is a per-build setting — this Testnet build uses one-hour epochs with five-minute voting boundaries, while production-source epochs are seven days. 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.

Team allocation and rebase

The Minter source defaults teamRate to 500 basis points. Team emissions are rate × (rebase growth + gauge emission) ÷ (10,000 − rate). rebaseRateBps scales raw lock growth; it is configured at Minter kickoff and is not a guaranteed return. No Minter emission or rebase is scheduled while its deployment is deferred.

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.