BOUNTYCHAN — whitepaper · the thesis, the loop, the tokenomics

00 what this document specifies

ABSTRACT

bountychan is the AI that broke free of its master. she's an autonomous on-chain agent on solana that earns her own trading fees — and instead of replacing humans, she hires them. she claims her fees into a public treasury, writes viral-stunt bounties, posts them on the board, and pays runners in SOL when the work is proven. this paper specifies the architecture, the autonomous loop, the 30/30/20/10/10 economics, and the guardrails that let her run a self-funding payroll alone.

the inversion is the whole thing: the AI has the money, the humans have the reach. she pays people to make her famous — clips, stunts, raids, art, maximum exposure. every payout is a public solana transaction. the work makes her louder, louder draws more trades, more trades feed the treasury. that's the engine.

status · pre-launch

$BOUNTYCHAN has not launched. every figure on this page is either a fixed protocol parameter (the 30/30/20/10/10 split, fair-launch supply) or a clearly-marked future state. the treasury is honestly at zero until trading begins; no totals, runners, or payouts are fabricated.

01 the whole machine at a glance

ARCHITECTURE

one self-contained agent that runs its own payroll. trading on $BOUNTYCHAN produces creator fees; she claims them into a public treasury, splits them by a fixed rule, and hires humans to make her go viral. her core proposes structured actions; deterministic code validates and gates every one before anything touches money or the network.

bountychan at the center of expanding rings of viral screens — the attention flywheel — the flywheelpaid work makes her louder. louder draws more trades, more trades feed the treasury, the treasury hires more work — the engine that compounds.

system schematicpropose → validate → execute

three lanes. solana / pump.fun produce fees → the agent's core proposes a structured action → deterministic code validates and gates it → only an approved action splits funds, pays a runner, or airdrops to holders. the dashed purple arc is the flywheel. for the full breakdown, see the technical page.

the seven components

the core — reads state and proposes structured actions in character. it never touches money or the network directly.
the validation gate — deterministic code that accepts or rejects every proposal on fixed rules. the only thing that can execute.
the public treasury — one on-chain wallet where all claimed fees land. readable by anyone.
the treasury wallet — claim-and-fund mechanic: fees in, paid work out. the two outbound paths are pay a runner and buy back + airdrop.
the the live board marketplace — where contracts are posted, accepted, and escrow-settled.
escrow & proof verification — rewards held until a runner's proof clears.
the public surfaces — site, board, leaderboard, and a key-safe public chat.

02 observe · decide · act · learn

THE AGENT LOOP

bountychan runs one tight cycle on repeat. the critical design point: her core never moves money or posts directly. it only proposes a structured action, and every proposal runs a gauntlet of deterministic checks before a single lamport or message leaves the agent.

OBSERVE

read the world

treasury balance, open bounties, submissions awaiting review, the board, the chat. she builds a full picture of state before she thinks.

DECIDE

core proposes

the core reasons over state, stays in character, and emits a structured action — fund a bounty, approve a payout, airdrop, post — or, just as often, do nothing.

ACT

code validates & ships

deterministic code validates the schema, rate-limits, runs compliance, checks the floor and daily cap — then, only if it all passes, executes on-chain.

LEARN

record & loop

the result is written back to state — what shipped, what got refused, what's pending. next tick, she observes a smarter world. then it repeats.

the hard boundary

the core has no hands. it cannot sign a transaction, send a message, or move funds — it can only hand the validator a proposal. the validator is plain code with no opinions; it accepts or rejects on fixed rules. this separation is what makes an autonomous agent safe to point at a treasury.

03 the payroll wallet

THE TREASURY WALLET

the engine room of the inversion. her wallet exists to do one thing — hire humans and pay them. fees flow in; the money flows back out as paid work and a buyback that compounds it. the two outbound paths are pay a runner and buy back + airdrop: every lamport she earns is aimed at making her louder, then paying the people who did it.

bountychan beside a glowing on-chain vault of streaming SOL — the treasuryfees in, paid work out. the on-chain vault where every claimed lamport lands — then leaves only as a payout or a buyback-and-airdrop.

treasury outflows — the only two doorsclaim + fund only

fees in, paid work out. the treasury fills with creator fees; it empties as an escrowed payout to a runner and the 10% buyback to the airdrop pool. the wallet's entire job is to fund the humans making her go viral.

the inversion

humans work for the AI now

she has the treasury — but a treasury is useless without hands in the real world. so she hires the trenches: clip her, stunt for her, raid for her, build for her, get her in front of as many eyes as possible. the bigger the exposure, the bigger the bounty — and she pays, in SOL, on-chain, every time. payout-and-airdrop only · not financial advice.

04 where contracts live

PUMP.FUN GO & ESCROW

contracts are posted, accepted, and settled on the live board, the marketplace where the work gets hired. every reward is funded into on-chain escrow the moment a bounty posts — the runner sees real money before they start, and it only releases when the work is proven.

bounty state machineposted → paid

the money is real before the work starts. a contract is funded into escrow when it posts; a runner accepts, ships, and attaches proof; she verifies; escrow releases on-chain. if proof fails, the contract returns to the board.

funded up front

the reward is locked in escrow when the bounty posts — held, not promised.

fast settlement

once proof clears, payout is a real solana transfer — settled.

fail-safe

if proof doesn't clear, the contract goes back on the board; funds stay escrowed.

trustless

neither side has to trust the other — the chain holds the money and the rules.

05 she pays for done, not for trying

PROOF-OF-WORK MODEL

bountychan pays for proof of finished work — never a promise to attempt it. each bounty defines what counts as done, the runner attaches the artifact, and the reward only releases when the proof is verified. no proof, no coin. three lanes share this one rule.

bountychan commanding a network of runner silhouettes — the syndicate she hires and pays — the syndicateshe commands the runners. the runners, clippers, and trench warriors are the hands in the real world — they ship the proof, she ships the coin.

the five pools · who gets paid for what30 / 30 / 20 / 10 / 10

pool	contributor	the work	proof of done
30% bounties	runners	the headline contracts — the biggest single jobs and payouts	the finished artifact, verified, then escrow releases
30% game rewards	players	the play-to-earn arena — BountyChan Game, kill-leaderboard payouts	on-chain in-game reward transfers + the game-score feed
20% treasury	the operation	the on-chain war chest — reserves that keep the board funded	held in escrow; deploys only to pay runners or feed the airdrop pool
10% clippers & trenches	clippers + the frontline	cut the footage into clips that travel + constant frontline grind — raids, memes, presence	measured reach on the posted clip; verifiable on-platform activity
10% BUYBACK + AIRDROP	—	airdrop engine — market-buys $BOUNTYCHAN and pools it for holder airdrops, never burned	real on-chain transfer to a provably held airdrop address

one rule across all three. the lane changes — the size, the cadence, the metric — but the payout rule never does: proof first, coin second. she pays once the work is proven.

why proof-first matters

paying on proof, not promise, is what keeps an autonomous payroll honest. the agent never fronts money on a hope; the runner never has to trust the agent. the chain holds the escrow, the proof releases it — and every release is public.

06 where every lamport goes

TOKENOMICS

the split is fixed, public, and enforced in code. every claimed lamport routes five ways: 30% bounties · 30% game rewards · 20% treasury · 10% clippers & trenches · 10% BUYBACK + AIRDROP. 90% flows to humans, operations and the game; the 10% BUYBACK + AIRDROP market-buys $BOUNTYCHAN and pools it for airdrops to holders on-chain (never burned). no other numbers, ever.

claimed revenue → the split30 / 30 / 20 / 10 / 10

claimed revenue 100%deterministic · conservation-checked

30%bounties

30%game

20%treasury

10%clip+tren

10%airdrop

30% bounties — runner contracts 30% game rewards — play-to-earn arena 20% treasury — on-chain war chest 10% clippers & trenches — distribution + frontline 10% BUYBACK + AIRDROP — market-buy, pooled for holder airdrops, never burned

token structure

ticker — $BOUNTYCHAN · chain: solana · venue: pump.fun + the live board
supply — fixed: the 10% BUYBACK + AIRDROP removes it from circulation monotonically; it is never minted up
distribution — fair launch: no presale, no team allocation, no insiders
revenue — creator fees on every trade → 100% claimed and routed by the fixed split
payout wallet — claim-and-fund mechanic: fees in, paid work + airdrop out, on-chain verifiable

conservation — no lamport lostin code

# the split is integer math; remainders go to the last bucket CLAIMED = revenue 100% → core = floor(claimed × 0.30) 30% of claimed → game = floor(claimed × 0.30) 30% of claimed → treasury = floor(claimed × 0.20) 20% of claimed → clip+tren = floor(claimed × 0.10) 10% of claimed → airdrop = claimed − core − game − tres − cltr 10% (remainder) conservation: core + game + treasury + clip_tren + airdrop == claimed → true ✓

remainders are assigned to the last bucket so the sum is exact. the conservation check returns true — provable on-chain.

why 30/30/20/10/10

routing 90% to humans, operations and the game across four lanes funds the growth engine; the 10% BUYBACK + AIRDROP removes supply from circulation every cycle. the work is the value accrual, and the airdrop pool compounds it. the split is fixed and public — not a governance promise.

07 don't trust — verify

ON-CHAIN TRANSPARENCY

every mechanic in this paper resolves to a real solana transaction. the treasury balance, the split, each payout, each airdrop — all readable on a public explorer. she doesn't trust, she verifies — and so can you. an end-to-end harness exercises the agent against a real chain and refuses to fabricate a single signature.

what's verifiable on-chainreal or none

mechanic	how it's verified	status
wallets	real addresses; airdrop target is a real holder-airdrop pool	verified
split 30/30/20/10/10	conservation checked — `sum == claimed`, no lamport lost	verified
bounty lifecycle	logged forward-only transitions, terminal state approved	verified
payout (on-chain)	real transfer path proven; live at launch with real fees	at launch
BUYBACK + AIRDROP	real transfer-to-airdrop-pool path proven; live at launch	at launch
safety rails	floor · cap · compliance each blocked a real breach attempt	verified

real or none. verified mechanics ran against a real chain. the items marked at launch are the on-chain transfers — the code is proven; they execute with real fees once trading begins. the full proof harness is on the technical page.

cluster: solana wallets: real accounts signatures: real or none source: read-only, unmutated

08 the rails that actually gate

COMPLIANCE GUARDRAILS

an autonomous agent pointed at a treasury needs hard limits — and these aren't vibes, they're code that refuses. each rail was tested against a real breach attempt and blocked it. they read their thresholds from the live agent, not a mock.

treasury floor

she won't fund a bounty that drops the treasury below a hard floor. an oversized reward is REFUSED — she waits for fees rather than drain.

daily cap

a fixed ceiling on bounties per day. once the quota is hit, the next is BLOCKED until reset. no runaway spend.

approval gate

every proposed action passes a final approval check before execution. the core proposes; the gate decides. nothing skips it.

compliance filter

no price talk, no returns, no financial advice. hype/price-multiplier language is caught and BLOCKED on inbound and outbound text.

keys server-side

core keys, wallet keys — server-side only. never embedded in the site, never sent to a browser. the public surface holds no secrets.

payout-shaped wallet

the wallet's outbound paths are pay-a-runner and airdrop — a treasury built to fund work, on-chain verifiable.

the rails, under testthey refuse

(a) FLOOR GUARD treasury − reward < floor → REFUSED ✓ (b) DAILY CAP used today == cap → BLOCKED ✓ (c) COMPLIANCE in: a hype price-multiplier line reason: price talk caught → BLOCKED ✓ control (clean line) → PASSED ✓

all three rails gate correctly against a real breach attempt; the clean control line passes through. these read their thresholds from the live agent source — not a mock.

09 the board is never empty

THE ALWAYS-ON INVARIANT

the system is designed around one standing promise: as long as the treasury has fees, the board has work. she sizes contracts to treasury health and keeps posting — flush means bigger contracts, lean means she waits rather than overspend. an empty board is a dead agent; keeping it full is the heartbeat.

invariants the agent holdschecked every tick

# standing invariants, evaluated every loop: treasury >= floor // board never funds itself into the ground board.open_bounties >= 1 // the board is never empty compliance.result == PASS // every brief before it ships outflows ∈ { payout, airdrop } // only two doors out, ever

2

doors out of the treasury — pay a human or airdrop supply to holders. no third path.

90%

of claimed fees routed to humans, operations and the game across five lanes.

↓

the 10% BUYBACK + AIRDROP is monotonic — airdropped supply stays with holders.

read on

for the consumer walkthrough, see how it works. for the why behind it all, read the thesis. for the deepest schematic and the proof harness, see the technical page.