TaifoonTAIFOON
TaifoonTAIFOON
15RPC PROVIDERS

RPC Providers

TL;DR
RPC Operators integrate Taifoon to enable trustless cross-chain operations. Verify events from any of 41 supported chains using cryptographic MMR proofs that your smart contracts can verify on-chain.
Return RPC responses with Taifoon proofs. Enable users to verify data without running full nodes.
ICP-03 · INFRASTRUCTURE & DATA

Off-Chain Infrastructure Mapping

DePIN · Oracles · RPC Nodes · Indexers
POTENTIAL USERS
DePIN
Helium · Filecoin
ORACLES
Chainlink · Pyth
RPC
Infura · Alchemy
INDEXERS
The Graph · custom
ENERGY GRID
IoT · Sensors
PROOF FLOW
01Physical / Cloud Signal
Energy · Compute · Sensor
02Taifoon Indexing
Bloom filter · MMR anchor
03Proof-Backed Response
Data + inclusion proof
04On-Chain Verification
SuperRoot binding
41 chains
indexed
bloom
filter per block
gRPC
streaming API
0 trust
assumptions
Pain Points RPC Operators Face
  • Trust Requirements: Users must trust RPC providers to return accurate data
  • Data Tampering: No way to prove RPC responses match on-chain state
  • Competitive Differentiation: Hard to differentiate from other RPC providers
  • Enterprise Customers: Institutions require verified data
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
1
Deploy TaifoonUniversalVerifier
Deploy the verification contract on your target chain:
forge create TaifoonUniversalVerifier \
  --rpc-url $RPC_URL \
  --private-key $PRIVATE_KEY
2
Create Proof Subscription
Subscribe to events from source chains via API
3
Implement verifyAndExecute()
Add verification logic to your contracts
4
Test and Deploy
Test on testnet, then deploy to production
Next Steps