Your Kaspa doesn't sit in a Stag Hunt wallet. When you back a hunt, it goes into an on-chain covenant UTXO whose rules are compiled into the script at the moment the hunt is created. The platform holds no key. Nobody at Stag Hunt can move the funds.

Funds leave the escrow in only two ways:

• A referee supermajority co-signs a release to the winning claimant's address, or
• A refund is triggered by the hunt's own rules (funding goal missed, or claims window closed with no winner).

The covenant enforces both paths. Even a malicious majority of referees can't send funds to an arbitrary address — only to the claimant the script recognises as the winner.

Referees are a curated whitelist of trusted Kaspa community members. They're the only parties whose signatures count toward a release or refund.

Frozen at hunt creation.Whoever is on the whitelist when the hunt is posted becomes its permanent jury — the covenant commits to those specific keys. Later additions or removals don't affect an already-running hunt.

Referees sign vote messages with a single-purpose burner Kaspa address. They never see or hold backer funds.

1. Write it.Give it a short, plain action title — just what someone has to do (e.g. “Run a Kaspa billboard in Times Square”). The prize is set separately, so never put it in the title. Add a funding window, claims window, and clear criteria referees can check against.
2. Fund it.Backers pledge Kaspa into the covenant escrow. If the funding goal isn't hit by its deadline, every backer is refunded to their contributing address (minus the on-chain fee).
3. Hunt starts. Once the goal is hit, the pot is locked and claims open.

1. Submit. Anyone can submit a claim with evidence plus the Kaspa address that should receive the pot if they win.
2. Referees vote. The first claim to reach a simple majority of the frozen referee set wins the whole pot — the moment quorum is hit, no waiting period.
3. Release.Referees co-sign a release transaction that the covenant accepts only if it sends the pot to the winning claimant's address.

Referees aren't required to approve the first submission — they can hold off on a YES if they think a better claim is coming. This is the platform's quality lever, enforced by referee culture rather than code.

1. A claim passes within the window. Pot releases to that claimant. Hunt closes. Other pending claims voided.
2. The claims window closes with no passing claim. Every backer is refunded automatically. The covenant only accepts a refund transaction that routes to the original contributing addresses.

Each backer gets their own refund transaction back to the address they contributed from, minus the on-chain network fee. Refunds are not batched into a single tx — this keeps each backer above the dust floor and avoids Kaspa's KIP-9 fan-out penalty. Any backer can initiate their own refund if the platform is down, because the refund condition is enforced by the covenant, not by a platform action.