What API3 now confirms

API3’s current website says new staking rewards are no longer distributed. Tokens already staked retain their vote, and rewards earned before the change continue vesting. The project directs holders to the existing DAO dashboard to unstake and withdraw as tokens unlock.

Its token page states that the final mint brought total supply to 200 million API3, with no remaining minters and ownership transferred to the dead address. Those are the project’s published contract-status statements. They describe token issuance, not a guarantee about market price.

Earned rewards still have an unlock schedule

The migration proposal, version 1.0 dated October 29, 2026, preserves the existing staking pool for exits. It specifies that the unstaking waiting period remains one epoch, or seven days, and that previously earned rewards retain their one-year vesting schedule. Ending new rewards therefore does not make every locked balance immediately withdrawable.

Holders can use the DAO dashboard linked from API3’s official homepage to check the balance and unlock information applicable to their wallet. The current notice distinguishes withdrawing unlocked tokens from the continuing vesting of earned rewards.

Voting moves to Snapshot

API3’s token page describes one API3 as one vote on Snapshot. The charter sets a seven-day vote and a quorum of 10 million API3 voting in favour. Execution is handled through multisignature wallets under the charter, rather than a Snapshot result automatically executing itself on chain.

The treasury page identifies the Treasury, Vault and Agent wallets as three-of-five Safes whose signers are bound to the charter through the API3 Foundation. Voting and execution are separate stages.

The dates behind this explainer

The official tracker marks primary proposal 17 as executed and labels October 29 as its start date. It also states that the old Aragon DAO has moved to Snapshot and staking rewards have ended.

This guide checks the published rules on November 12. October 29 is the proposal date, not an execution timestamp; the tracker view checked here does not give an execution date. The transition is not presented as a new November 12 announcement.