Guide · updated 2026-10-24

How Anoma governance works

XAN holders govern Anoma through a Governor contract on Ethereum: they delegate voting power, propose, vote, and a timelock carries out what passes. This guide sets Anoma's own description of Governance V2 beside the rules as the explorer reads them from the contracts, and shows how to check them yourself.

What Governance V2 changed

According to Anoma's announcement, Governance V2 puts Anoma's direction, its parameters and its future code in the hands of the people holding XAN. It lifts the governance logic out of the XAN token and rebuilds it as a DAO: proposals, voting and execution now run through a dedicated governance contract built on OpenZeppelin's Governor framework. Holders can propose and vote on changes to the XAN token protocol, including its supply, how it works, the treasury and the governance settings themselves. In the first version, described when XAN launched, holders locked tokens to vote on protocol upgrade proposals, and a vote weighed in proportion to the tokens locked behind it. That logic sat inside the token itself, which the V2 announcement says made it rigid and awkward to improve. [1] [2]

The rules as Anoma announced them

Proposal threshold
How much XAN a holder needs to create a proposal: at least 25,000 XAN, which Anoma says keeps the queue clear of spam. A proposal is public from the moment it is created. [1]
Review period
Seven days between the creation of a proposal and the start of voting. Anoma's announcement calls it the review window. The Governance page labels this step Review and reads its length from the contract's votingDelay(). [1]
Voting period
Fourteen days in which holders vote For, Against or Abstain. Each vote weighs in proportion to the voter's balance. [1]
Quorum
The turnout a vote needs to count: at least 10% of the voting supply must take part. A proposal passes when it reaches quorum and has more For votes than Against. [1]
Timelock
A fourteen-day waiting period that every approved proposal sits through before it takes effect, so no upgrade lands without public notice first. After the wait, any address can trigger execution. Anoma's announcement says the timelock controls the XAN token and is the only thing able to change it. [1]
Upgrade council
A multisig that exists only as a backup. If turnout ever falls so low that nothing can reach quorum, it can schedule critical upgrades so the protocol does not freeze. A council upgrade takes 42 days, longer than the path through a vote, and holders can cancel it in that time. Holders can also replace the council or remove its permissions, and the council cannot block that. [1]
End to end
Roughly 35 days from proposal to execution: seven days of review, fourteen of voting and fourteen in the timelock. [1]

The same rules, read from the Governor contract

The explorer does not copy these rules from the announcement. About once an hour it asks the Governor contract on Ethereum for votingDelay(), votingPeriod(), proposalThreshold(), quorum() at a recent timepoint and the quorum fraction (quorumNumerator() over quorumDenominator()), and asks the timelock for getMinDelay(). The Governance page shows the answers in its How a proposal moves card, and its Proposal to execution figure adds the review, voting and timelock durations together. The same values are in /api/v2/governance under params, and readAt gives the time of the read. Durations are in seconds; the threshold and the quorum are XAN in base units, like every amount in the API. When this guide was last checked, the values read from the contracts matched the announcement. To check them yourself: [1]

  1. Find the Governor, the timelock and the XAN token in the Contracts card on Governance, or under contracts in /api/v2/governance. All three are on Ethereum.
  2. Open the Governor in any Ethereum block explorer's read-contract view, or send an eth_call through any node, and read votingDelay(), votingPeriod(), proposalThreshold(), quorumNumerator() and quorumDenominator(). On the timelock, read getMinDelay().
  3. Compare the answers with params in the API and with the announced rules above. Durations come back in seconds, so divide by 60 × 60 × 24 to get days.
  4. Read owner() on the XAN token and compare it with the timelock's address. The token card on Governance makes the same comparison.

Why XAN counts as votes only once delegated

Voting power only counts once it has been delegated.

anoma.net

Holding XAN is not enough on its own. A holder first delegates: to itself, to vote directly, or to another holder, who then votes with that weight. Delegating takes one action and can be changed or taken back at any time. The announcement also says that locked tokens can still vote. Balances locked under the first version vest linearly over three years from 29 September 2026 at 12:00 UTC, and whatever has vested can be claimed at any point. Voting power covers the whole balance, vested or not. To take part, the announcement sends holders to portal.anoma.net, and the post that launched XAN describes the Anoma Portal as the place to view and manage XAN balances and to take part in governance. On Governance, the Voting power card follows the token's delegation events and shows the delegated total, the delegates and the latest delegations. The token card shows how much of the vesting period has passed, read from the token's own vestingStart() and vestingEnd(). [1] [2]

Where proposals are discussed

Discussion happens on the Anoma forum, in its Governance category. According to the category's opening post, it is the place to discuss governance changes to the Anoma protocol and its apps. Delegates can introduce themselves there: the delegate profile posted by Anoma Contributors, for example, describes that delegate as shared by the people building on and around Anoma, sets out how it decides its votes, and invites holders to delegate to it. The Governance page refreshes its list of the newest topics in the category every fifteen minutes. It links to them rather than copying them, so the forum stays the place to read and reply. [1] [2] [3]

Questions

How long does an Anoma governance proposal take?
Anoma's Governance V2 announcement puts it at roughly 35 days: seven days of review, fourteen days of voting and fourteen days in the timelock. The durations the contracts enforce right now are on Governance, read from the Governor and the timelock.
Why does my XAN have no voting power?
XAN counts as votes only once it is delegated, to your own address or to another holder, as Anoma's announcement explains. Delegating takes one action, can be changed or taken back at any time, and the announcement sends holders to portal.anoma.net to take part. The Voting power card on Governance shows which addresses hold delegated votes.
Can locked or vesting XAN vote?
Yes. Anoma's announcement says balances locked under the first version vest over three years from 29 September 2026 and vote with the full balance, vested or not. The token card on Governance shows how much of the vesting period has passed, read from the XAN contract.
How much XAN does it take to propose or to reach quorum?
Anoma's announcement sets the proposal threshold at 25,000 XAN and the quorum at 10% of the voting supply, and a proposal also needs more For votes than Against to pass. The values the Governor contract holds now are on Governance in XAN, and in /api/v2/governance in base units.
Is Gnoma Explorer part of Anoma governance?
No. Gnoma Explorer is independent and not affiliated with the Anoma Foundation or Heliax: it reads the public contracts and links to the forum. To take part in governance, Anoma's announcement sends holders to portal.anoma.net.

Sources

Gnoma Explorer is independent and not affiliated with the Anoma Foundation or Heliax. Statements about Anoma are Anoma's own, from the sources above; figures are this explorer's, from the pages linked in the text.

Read next: Governance · XAN, Anoma's token: what it is and how it is counted · XAN token · Anoma glossary: the terms in plain words · Anoma data without a key: the free API