TaifoonTAIFOON
TaifoonTAIFOON
11CROSS-CHAIN BRIDGE OPERATORS

Cross-chain Bridge Operators

TL;DR
Cross-chain bridge operators relying on multisigs, oracles, and committees can eliminate trust assumptions with Taifoon's cryptographic proof layer. Verify events from any of 41 supported chains using portable MMR proofs.
Bridges relying on multisigs, oracles, and committees face inherent security risks. Taifoon replaces these trust assumptions with cryptographic MMR proofs—enabling trustless cross-chain verification that your smart contracts can validate on-chain.
ICP-01 · DEFI PROTOCOLS

Protocol Verification Integration

DEXs · Lending · Perps · Yield · RWA
POTENTIAL USERS
DEX
Uniswap · Curve
LENDING
Aave · Morpho
PERPS
GMX · dYdX
YIELD
Yearn · Beefy
RWA
Centrifuge
PROOF FLOW
01Source Chain Event
Lock · Deposit · Trade
02MMR Proof Generation
L1 → L2 → L3 → L4 → L5
03SuperRoot Verification
On-chain, no bridge
04Protocol Execution
Mint · Release · Liquidate
~20 lines
to integrate verifier
<500ms
proof generation
41 chains
supported
0 bridges
required
Pain Points Bridge Builders Face
  • Multisig Vulnerabilities: Traditional bridges rely on multisigs that can be compromised
  • Committee Coordination: Managing validator committees is complex and expensive
  • Trust Assumptions: Users must trust bridge operators with potentially millions in assets
  • Security Incidents: Bridge hacks have resulted in $2B+ in losses across the industry
How Taifoon Solves It
Key Benefits
✓ No bridge multisigs or committees
✓ Cryptographic proof verification on-chain
✓ Support for 41 chains out of the box
✓ 4-step integration in 24-48 hours
✓ Pay per proof ($0.0006 - $0.0020 depending on chain)
4-Step Integration Walkthrough
01
Deploy TaifoonUniversalVerifier
Deploy the verification contract on your target chain
02
Create Proof Subscription
Subscribe to events from source chains via API
03
Implement verifyAndExecute()
Add verification logic to your contracts
04
Test and Deploy
Test on testnet, then deploy to production
CASE STUDY — BRIDGE INTEGRATION
Live bridge events — no polling required

Taifoon indexes real bridge crossings directly from the source contracts and pushes them over Server-Sent Events as they happen — an explorer, wallet, or another bridge UI subscribes once instead of re-running eth_getLogs against every chain on a timer. The GLMR and MOVR migration bridges (Moonbeam → Base) are the first two live feeds on this stream; any protocol we index can be added the same way.

Subscribe (all bridge protocols):
curl -N https://taifoon.io/api/intel/genomes/stream
Subscribe (GLMR migration only):
curl -N "https://taifoon.io/api/intel/genomes/stream?protocol=moonbeam-glmr-bridge"
Subscribe (MOVR migration only):
curl -N "https://taifoon.io/api/intel/genomes/stream?protocol=moonbeam-movr-bridge"
FieldMeaning
event_kind"deposit" when the source chain lock fires, "settle" when the destination delivers
src_chain_id / dst_chain_id1284 (Moonbeam) → 8453 (Base) for both GLMR and MOVR
src_tx / dst_txThe real transaction hash on each side, once known
amount_rawAmount in the token's native decimals, as a decimal string
route_hashStable identifier for this (src, dst, token, protocol) route — group by this to reconstruct a route's full history
One request for the whole picture — /api/protocol/:slug/overview

Order tracking, protocol analysis, and the live event stream used to be three separate systems with no single subscription model. This composes them: current order counts by state, the same volume/holders/solvers analysis the intel API serves, and a pointer to the exact SSE endpoint to subscribe to for this protocol — one GET instead of four.

Get the full picture for one protocol:
curl https://taifoon.io/api/protocol/wormhole/overview
FieldMeaning
foundtrue if this protocol has either a catalogued analysis dossier or at least one real tracked order
analysisVolume/holders/solvers/finality — the same dossier /api/intel/protocol/:slug serves, or absent if not catalogued
orders.total / orders.by_stateLive order counts, matching this protocol under either its canonical slug or any internal versioned alias (e.g. "across" also counts "across_v3" orders)
orders.scan_truncatedtrue if the order store is too large to scan completely within the request — when true, orders.total is a lower bound, not a complete count
genome_stream.endpointThe exact SSE URL to subscribe to for this protocol's live events — a pointer, not embedded data (the stream has no history, only a live push)
WANT YOUR PROTOCOL ON THIS STREAM?

If you run a bridge, DEX, or any cross-chain protocol and want your crossings surfaced the same way — pushed to subscribers instead of everyone re-scanning blocks — send us the contract addresses, chain IDs, and event ABI for the deposit/settle pair you want indexed. Reach out via Telegram or open an integration request — see the integration hub for every other way to reach Taifoon's data.

Next Steps