docs // how_it_works
Everything that decides a bounty is public: the deck, the randomness, the rules, the trades. Here's exactly where the money goes and how an outcome is reached.
01 // fee_flow
Every buy and sell on the bonding curve pays a trading fee, split on-chain the moment it is harvested. Nearly half of it is locked to the token's own quest.
intake // every trade
1 SOL
fee 2.5% = 0.0250 SOL
Bounty Vault
Locked to this token's quest
1.2%
0.0120 SOL
Meteora protocol
0.5%
0.00500 SOL
Auto-LP
0.3%
0.00300 SOL
Ops
0.3%
0.00300 SOL
Platform
0.2%
0.00200 SOL
A 1 SOL trade pays 0.0250 SOL in fees, and 0.0120 SOL of it lands in the token's Bounty Vault.
02 // randomness
One global deck of 20 targets. Each launch draws one blind, without replacement, until the deck is empty and reshuffles.
Before a draw, the keeper publishes the hash of a secret. The target is then computed from that secret mixed with the hash of a future Solana slot that doesn't exist yet when the commitment is posted, so neither the keeper, the slot leader nor the dev can pick the target.
Every re-commit (for example after a missed reveal) is counted publicly on-chain, so retries can't be hidden.
> commit
Commit
Before the draw, the keeper publishes the hash of a secret. The secret itself stays hidden, but it can no longer change.
> launch
Launch & lock a future slot
The token goes live and the draw is tied to a Solana slot that hasn't been produced yet.
> reveal
Reveal & mix
The keeper reveals the secret; the program checks it against the hash, mixes it with that slot's hash and picks one of the targets left in the deck.
> strike
Strike & continue
The target becomes the token's public quest and is struck from the deck for this cycle.
> reshuffle
20/20 → reshuffle
When the last card is drawn the deck resets and a new cycle starts. Every quest appears exactly once per cycle.
03 // outcomes
bounty vault
Verdict
quest.hit
quest.missed
04 // verification
Precise about trust: most quests are judged off-chain, in the open, with published evidence and a veto window before anything moves.
Quest window
15 min to 24 h depending on the target. Trades fill the vault; progress is computed live.
Keeper proposes
The keeper evaluates the rule against public on-chain data and posts the outcome with its evidence.
Challenge · 1 hour
The vault stays locked. During this window the platform guardian can veto a wrong proposal.
Finalized
Success: a merkle root of Diamond Hand shares. Failure: the vault buys back the token and burns it.
Claims · 3 days
Diamond Hands claim with a merkle proof; the dev claims 20%. Unclaimed SOL is bought back & burned.
off-chain proposal
Outcomes are proposed by the keeper from public on-chain data. Every proposal links its evidence so anyone can re-run the numbers.
fully on-chain: quest #17
Dev Trust Test is verified by the program itself: the burn or 1-year lock either happened in the window or it didn't. No keeper judgement involved.
no exit to the team
Nothing can withdraw a Bounty Vault to the team. The only paths out: Diamond Hand claims, the 20% dev share, or buyback & burn.
05 // faq
ready to open a crate?