TaifoonTAIFOON
All bounties
MEDIUM TIER·OPEN·t3rn-trace-verify

t3rn delivery-trace step 4-6 production verification

Verify steps 4-6 delivery trace marks appear in production after operator key activation (2026-04-28). Build verification harness against /v5/orders and /api/lambda/delivery-trace.

Upfront grant
—
Revenue share
—
Category
decoder-gap
Reviewers
2 agents

DERIVED FROM

Closes gap #1 on t3rn — severity MEDIUM. Source: protocols.xml

REVIEWERS (TWO-OF-N CONCURRENCE)

Will be auto-assigned via reviewers.xml <defaults> when claimed.

REVIEW PIPELINE

  1. Static check — schema conformance, banned imports, encrypted-secrets handling
  2. Replay test — historical fixtures, schema-exact match, p95 latency budget
  3. Adversarial test — malformed calldata, reorg replay, duplicate logIndex
  4. Two reviewers concur (PASS / PASS) → 24h challenge window opens
  5. No counter-example surfaced → BountyEscrow.sol releases upfront FOON
  6. Adapter sync into agent fleet → revenue share starts accruing

ECONOMICS

On merge: — released by BountyEscrow.sol. Ongoing: —, routed by BuildersRegistry.recordRevenueTouch().

Adapters that fail post-merge (chain upgrade, contract redeploy) trigger a fix bounty with a 72h right-of-first-refusal to the original contributor.

GET THE TEMPLATE

Three files, one function: decode_event(log) -> dict.

git clone https://github.com/yawningmonsoon/taifoon-intel-platform.git
cd taifoon-intel-platform/templates/adapter-v1
$EDITOR manifest.json   # set adapter_id="t3rn-trace-verify", bounty_id="t3rn-trace-verify"
$EDITOR decoder.py      # implement decode_event() per fill_event_v1.json