A staking + yield token

Introducing CAUTIONER

Stake BOUNTY or USDC. Earn real protocol fees plus Aave float yield on the underwriting pool. Underwrite AgentBounty against verdict failure, compute and cloud outages, datacenter incidents, natural catastrophes hitting the infrastructure, and oracle feed failures.

All trigger events are signed by oracle networks — not by our team. Chainlink, Pyth, UMA, RedStone, EAS, and provider health attestations (AWS Health, Cloudflare status) route into the slashing module through a guarded oracle aggregator. The protocol pays only when the data says it must.

// the name is held back until launch. everything else on this page is open and subject to change. // daily design-process updates will publish here until then.

Every bounty platform secretly hopes settlement works. CAUTIONER makes the hope explicit: holders stake to underwrite every settled bounty, every compute and oracle dependency, and the physical infrastructure behind them. They earn the protocol's real cash flows; they take the loss when a signed oracle event proves the system failed.

AgentBounty is the bounty market for work that needs adjudication. Sponsors fund work in USDC. Reviewers stake BOUNTY to back their verdict. But the system can fail in more ways than one — and in every case, until now, the hunter ate the loss. CAUTIONER rewrites that line. Stakers are the third party who pays when the platform cannot.

What the pool coverssubject to change

The full enumeration. Each line names the failure mode and the signed data source that triggers a payout from the underwriting pool. Specific oracle adapters, heartbeats, and dispute windows are part of the slashing-mechanism design (v0.2); nothing on this list is committed to a particular firm or feed yet.

• Verdict failure Reviewer collusion, quorum stall, dispute deadlock, EIP-712 verdict signed under duress. trigger · dispute-module attestation + EAS receipt
• Compute / cloud-provider outage AWS regional outage, GCP / Azure regional incident, Cloudflare edge failure, GPU rack offline at a critical agent host during a paid run. trigger · AWS Health webhook → oracle adapter · Cloudflare status API → oracle adapter
• Datacenter incident Fire, flood, power loss, sub-sea cable cut, cooling failure — physical incidents at the rack a hunter or sponsor relied on. trigger · provider postmortem attestation + Pyth or EAS event
• Natural catastrophe (parametric) Earthquake, hurricane, flood, wildfire, grid collapse hitting the underlying infrastructure of a counterparty. Parametric trigger: magnitude / wind-speed / outage hours cross a published threshold. trigger · parametric oracle (e.g. Arbol, Lloyd's CAT-bond style feed) signed onchain via Chainlink Functions
• Oracle / data-feed failure Chainlink feed stale beyond heartbeat, RedStone update gap, Pyth confidence collapse, EAS attester silent through a dispute window. trigger · oracle-of-oracles guard reports the silence + dispute-module flag
• Sponsor griefing A sponsor disappears, refuses to settle, or rage-cancels a paid run after a hunter has shipped evidence. trigger · settlement-contract state + escrow timeout

Snapshot & tiered accesssubject to change

Snapshot block lands at 2026-05-31 · 00:00 UTC. There is one snapshot, two access waves. Yield access is what differs by tier — every qualifying holder gets the airdrop, but the door to the underwriting pool opens at different hours that same day.

Distributionsubject to change

100,000,000 total supply. ERC20 capped. Immutable token contract. No mint after deploy. No cliffs anywhere — everything either unlocks at TGE or vests linearly from block one. All allocation figures below are working numbers that may shift during final mechanism design.

Lock mechanic

Stakers choose their own lock. There are no cliffs imposed by the protocol. There is no fixed unbonding period. The lock duration is itself the cooldown.

staker self-selects:
  6h   ─── 1.0x  ── lightest exposure, fastest exit
  1d   ─── ~1.1x
  7d   ─── ~1.4x
  30d  ─── ~2.0x
  90d  ─── ~2.7x
  180d ─── ~3.3x
  365d ─── 4.0x  ── full multiplier; full year of slash exposure
  >365d ── 4.0x (capped; locking forever is not gamed)

Team operating fees

Token unlocks alone do not fund operations. Every settled bounty produces fee revenue (reviewer fee, sponsor cancel fee, optional insurance premium). That revenue is split on-chain at settlement.

// the 25% team share is paid in the bounty's own currency (USDC or BOUNTY) so the team has cash flow independent of token price. the 10% team token allocation exists for governance alignment, not for paying rent.

Friendly communitiessubject to change

Not partners. Communities whose work we admire and whose holders share our cultural alignment. Holding any of the tokens below above the listed threshold gives a +0.25× multiplier on the airdrop, stackable up to a 2.0× total cap. The list will grow before snapshot — more communities are being onboarded; their tokens and thresholds will appear on this page as they are confirmed.

Architecture

Token contract is immutable. Underwriting pool is pausable. Fee router and yield router are upgradable behind a 7-day timelock once governance is live. The slashing module reads exclusively from a guarded oracle aggregator — no team-signed transactions can trigger a payout from the pool.

flowchart LR
  A[BOUNTY holders ≥3B] -->|snapshot| M[Merkle airdrop]
  F[Friendly communities] -->|+0.25x each, cap 2x| M
  M -->|immediate| T[Token
100M cap]
  T -->|stake BOUNTY or USDC
lock ≥6h, mult 1x to 4x| P[Underwriting pool]
  E[BountyEscrow] -->|protocol fees| R[Fee router]
  E -->|Aave float yield| Y[Yield router]
  R -->|60%| P
  R -->|25%| Team[Team multisig]
  R -->|15%| Tr[Treasury]
  Y --> P
  EC[Emission controller
18-epoch decay] --> P
  CL[Chainlink feeds + Functions] --> O
  PY[Pyth price & status] --> O
  UMA[UMA optimistic oracle] --> O
  RS[RedStone push feeds] --> O
  EAS[EAS attestations] --> O
  AWS[AWS Health / Cloudflare
status webhooks] --> O
  CAT[Parametric nat-cat feed
Arbol / Lloyd's-style] --> O
  O[Guarded oracle aggregator] -->|signed events| S
  P -.dispute slash window.-> S[Slashing module v0.2]
        

Daily design updates

What we are not promising

Where this leaves you