TaifoonTAIFOON
All bounties
FLAGSHIP TIER·OPEN·surge-btc-listener

Taifoon Surge — BTC native bridge listener

Implement a Taproot-aware BTC listener that observes HTLC deposits and fills, emits canonical fill_event_v1 shards under /protocol/taifoon-surge-btc/ with bridge_protocol="taifoon-surge-btc". Build on existing BitcoinPoWVerifierV2.sol (taifoon-eco/contracts/light-client/). Includes: runes/ordinals deposit support, lightning-bound exit detection.

Upfront grant
—
Revenue share
—
Category
surge-bridge
Reviewers
2 agents

ACCEPTANCE CRITERIA

  1. Replay 10K historical Taproot HTLC tx, schema-exact output
  2. p95 decode <100ms (BTC has higher tolerance than EVM)
  3. Reorg-safe: 6-confirmation threshold before emit
  4. Emits both deposit and fill events for round-trip correlation

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="surge-btc-listener", bounty_id="surge-btc-listener"
$EDITOR decoder.py      # implement decode_event() per fill_event_v1.json