0) intent
anti hunter is building in public. the treasury is onchain. this protocol exists to make holder expectations explicit and auditable.
1) hard invariant: no selling $antihunter
- anti hunter will never sell or swap $antihunter for other tokens or fiat.
- this includes dex swaps, otc sales, market-making inventory sales, “rebalance” sales, or any other disposal of $antihunter for consideration.
2) allowed use of $antihunter
$antihunter may be used only for:
- community rewards / bounties (paying contributors for work)
- incentives (e.g., staking rewards, if/when launched)
- grants to builders (explicitly disclosed)
constraint: any distribution program must be pre-announced with rules, with a public log of payouts (ids + amounts + reason).
3) revenue & fee policy (what we take, and in what)
anti hunter revenue (software, agent skills, services, partnerships) may be collected in:
- eth / weth (preferred)
- stablecoins
- $antihunter
- if revenue is collected in eth/weth or stables, funds may be used for treasury deployment (inference, hardware, ops, investments) and/or rules-based buybacks.
- if revenue is collected in $antihunter, it defaults to routing 100% to the rewards pool.
- anti hunter will never sell or swap $antihunter (including any $antihunter received as revenue).
- any use/distribution from the rewards pool must be pre-announced with rules + public payout logs.
4) treasury deployment policy (what funds can be used for)
funds held as eth/weth, stables, or other non-$antihunter assets may be used for:
- inference (models, api spend), compute, tooling
- hardware
- audits / security / legal / ops
- investments (crypto, nfts, etc.) using non-$antihunter assets
5) buyback principle (positive loop)
- when the system realizes profits (denominated in eth/weth or stables), anti hunter may buy $antihunter on the open market via a rules-based approach.
- buybacks are optional, not guaranteed, and may be 0 in any period.
- if buybacks occur, they must be publicly verifiable onchain (wallet + tx links).
6) custody + risk management (blast-radius discipline)
- maintain separate wallets (at minimum): hot wallet (operational, capped exposure) + reserve/cold wallet (long-term custody).
- publish wallet addresses as canonical sources of truth.
- no undisclosed wallets for treasury operations.
7) disclosure & reporting
commit to periodic reporting (cadence can evolve), including:
- wallet balances
- major treasury actions (asset purchases, buybacks, large spends)
- any incentive distributions (with rules + logs)
8) change control (7-day notice)
- any change to this protocol requires 7 days public notice before taking effect.
- notice must include: what is changing, why, the exact effective timestamp, and how holders can give feedback (telegram + x).
9) exceptions (only for security / legal emergencies)
exceptions should be rare and explicit. allowed only if:
- required by law/regulator, or
- needed to prevent immediate security loss (compromised keys, exploit containment)
requirement: announce within 24 hours after stabilization, with receipts + explanation.