Skip to main content
When a market outcome is disputed, $AURA stakers settle it through a commit/reveal vote. This tutorial walks through the voter’s experience from start to finish. If you haven’t read the conceptual overview yet, start with Resolution & Disputes. For the rules that govern voting power and slashing, see Staking & Vaulting $AURA.

​
Before you start

You need:
  • An Aura account (sign in with email or Google).
  • At least the Iron tier, meaning 60,000 vaulted AURA. See [Staking & Vaulting AURA](/tokens/staking).
You should also know:
  • Voting is not free. If you back the wrong outcome, 0.1% of your vaulted $AURA is slashed per vote. Vote on markets you’ve actually researched.
  • You sign one transaction, the commit. Aura’s reveal automation submits the matching reveal for you when the reveal window opens.
  • Your staked balance is snapshotted at commit time, so unstaking between commit and reveal doesn’t dodge the slashing risk.

​
Step 1: Find a disputed market

1

Open the Voting tab

From the top navigation, click Voting, then select the Outcomes sub-tab.
2

Pick an active dispute

Each disputed market shows the question, the proposed outcome, the challenger’s position, and the current phase (Commit / Reveal / Finalizing).
3

Read the resolution rules

Open the market detail and read the original resolution rules and sources. Your job as a voter is to determine which outcome the rules support, rather than which outcome you’d prefer.

​
Step 2: Commit your vote

The commit phase locks in your choice without revealing what it is. This prevents later voters from copying earlier ones.
1

Pick a choice

  • YES. The rules clearly resolve the market YES.
  • NO. The rules clearly resolve the market NO.
  • TOO EARLY. The underlying event hasn’t happened yet, the data source isn’t out, or the question is malformed. If this wins, the submitted outcome is thrown out and the market goes back to trading. Nothing is cancelled or refunded.
2

Click Commit

Aura generates a random salt (a one-time secret), computes keccak256(market || voter || choice || salt), and sends the hash on-chain. The salt + choice are also queued with Aura’s reveal automation, which will submit the reveal on your behalf during the reveal window, so you don’t need to come back.
3

Sign the commit transaction

Confirm in your wallet. The on-chain commit records:
  • Your hashed vote
  • Your tier weight at commit time
  • Your address (so the contract can match it on reveal)
You can commit any time during the commit window, but only once per vote round. If you change your mind after committing, you can’t re-commit, but you can choose not to reveal, which costs you the same 0.1% slash as voting wrong. Generally, only commit when you’re confident.

​
Step 3: Reveal (automatic)

Once the commit window closes, the reveal phase opens for a shorter window (typically about an hour). Aura’s reveal automation submits your original choice and salt on-chain, and the contract verifies the hash matches your commit before tallying your tier-weighted vote. You can watch the status of your queued reveal under Voting → Outcomes (or via GET /v1/users/me/pending-reveals, which reads your own queue only).
Prefer not to share your vote choice with Aura’s relay before it hits the chain? Commit through the API and reveal yourself with POST /v1/tx/oracle/reveal during the reveal window. The contract accepts a reveal from any caller, since the hash binds it to your address.
If your commit is never revealed in time (for example, a self-managed reveal that misses the window), you’re slashed the same 0.1% as a wrong-side voter. The contract treats silent commits as bad-faith participation.

​
Step 4: Wait for finalization

After the reveal phase, the protocol checks whether any single outcome cleared the 65% supermajority of revealed weight:
  • Cleared 65%. The market resolves to that outcome, traders are paid out, and the penalty pool is ready for claims.
  • Did not clear 65%. A new commit/reveal round starts, and you can commit again in it. Note that anyone who committed in the inconclusive round without revealing is slashed before the restart, so an inconclusive round doesn’t wipe the slate for silent commits.
If TOO_EARLY clears 65%, the submitted outcome is thrown out and the market goes back to trading. Nothing is cancelled or refunded, and trading fees stay with the market until it eventually resolves YES or NO. The disputer gets their bond back plus half of the proposer’s bond; the other half goes to the treasury. No voter rewards are paid on a TOO_EARLY round. The slashed $AURA rolls forward into the market’s next dispute round.

​
Step 5: Claim your reward

If you backed the winning outcome:
  • Your proportional share of the penalty pool is calculated from your tier weight relative to the total winning weight.
  • Rewards are paid in $AURA directly to your wallet, and Aura’s automation pushes the payout once penalties are finalized, so no claim transaction is required from you.
If you backed the losing outcome (or didn’t reveal):
  • 0.1% of your vaulted $AURA is slashed and added to the penalty pool for the winners.

​
Things to know

​
What “tier weight” means at vote time

The contract reads your tier from the Vault at the moment you commit, not at the moment you reveal. So if you stake more $AURA between commit and reveal, your additional stake doesn’t increase your weight for that round, but it does for the next round. Your staked balance is snapshotted at commit time too, so unstaking mid-round doesn’t reduce your slashing exposure.

​
Why the reveal window is shorter than the commit window

Once commits are locked, the only thing left is bookkeeping. A long reveal window adds delay without improving security, since the automation reveals queued votes promptly once the window opens. Stakers whose commits never reveal are signaling they wanted to influence the hash count without actually voting, which is exactly the bad-faith behavior the slashing penalty deters.

​
Can I vote on a market I’ve traded?

Yes. Holding a position doesn’t disqualify you, and a rule against it wouldn’t achieve much anyway, since anyone could sidestep it with a second wallet. What keeps votes honest is economics: the 65% supermajority requirement and the 0.1% slash for backing a losing outcome.

​
Quick checklist

  • I’m at Iron tier or higher.
  • I’ve read the resolution rules.
  • I’m confident enough to put 0.1% of my vault on the line.
  • My reveal is queued (automatic), or I know I must reveal manually within the window.
Last modified on July 29, 2026