DAO Governance
Players propose and vote on how the game is tuned. The DAO lets established accounts propose changes, sponsor the ones worth debating and vote them through, with thresholds set high enough that a passing vote represents the playerbase rather than a handful of large wallets. Every result is advisory: the team ratifies or vetoes each passing vote in writing.
Voting power
Your voting power is built from three parts. It starts from a snapshot when a vote opens:
- Held tokens — your lowest $AFKHERO balance during the vote, at 1 per token. Tokens waiting in the staking queue, or held for your auction bids and raffle tickets, count as held.
- Spending — every $AFKHERO you have spent in the game counts 2, so spending counts for more than simply holding.
- Staking — staked tokens count by lock length: 1.25 for a 7-day lock, 1.5 for 14 days and 2 for 30 days. A stake that has matured counts for nothing.
The per-account cap is the core protection: no matter how large a single holder is, their vote stops counting past the cap, so a proposal cannot be carried by one wallet. Power is linear, not quadratic, so splitting tokens across accounts gains nothing, and linked accounts are counted as one voter. During a vote your power can only go down — spending or unstaking mid-vote lowers it, and adding tokens does not raise it. A vote keeps the rules it opened with. The My Power panel in the DAO screen shows your current number.
Proposing
| Requirement | Value |
|---|---|
| Hero level | 50 |
| Voting power | 500,000 |
| Account age | 7 days |
| Proposals per account | 3 per 7-day window |
A proposal is either a Yes/No policy vote or an options vote with up to six choices. An options vote always adds "No change" and "Abstain".
Sponsorship and review
A new proposal does not go straight to a vote. It must first attract sponsorship within 72 hours: a combined 5,000,000 of voting power from at least 25 distinct accounts. This filters out proposals nobody supports before they use up the community's attention, and the distinct-account requirement means one large holder cannot sponsor a proposal alone. The team then reviews the proposal before it opens, and may decline proposals that touch money-critical systems such as emission, token supply, the treasury, prices or withdrawals.
Voting
Both kinds of vote must clear quorum on both measures: enough power and enough distinct voters.
Anti-snipe
A vote that shifts late is extended rather than decided in its final minutes. If at least a quarter of the voting power arrives in the final 3 hours, the voting period is extended by 3 hours. This can happen up to twice. Changing your vote is locked in the final hour, so the closing state cannot be flipped at the last second.
After a vote passes
The team ratifies or vetoes a passing vote in writing within 7 days. The outcome and the implementation status are shown on the proposal. Some changes are applied directly as configuration; others require a build.