TAIFOON16RELAYERS
Relayers
TL;DR
Relayers transport cross-chain messages but depend on trusted execution assumptions. Taifoon adds a cryptographic proof layer that enables trustless message verification — turning relayers into proof-backed transport systems with mathematical certainty.
Current relayer systems operate on trust: users assume messages are delivered correctly without cryptographic proof of execution. Taifoon solves this by providing verifiable message delivery proofs that any party can validate on-chain.
The Problem: Trusted Execution Dependencies
Relayer systems face critical trust assumptions:
- No Proof of Delivery: Relayers can claim messages were delivered without cryptographic evidence
- Censorship Risk: Malicious relayers can selectively delay or drop messages without detection
- Execution Guarantee Gap: Users cannot verify that source chain state was correctly interpreted on destination chain
ARCHITECTURE LIMITATION
Traditional relayer models assume honest execution because verifying remote chain state requires running full nodes on every chain — economically infeasible for most protocols. Taifoon's MMR proofs solve this with portable verification.
The Solution: Proof-Backed Message Transport
Taifoon transforms relayers into trustless proof carriers:
VERIFIED MESSAGE FLOW
01
Source Chain Event
User initiates cross-chain action (transfer, call, message)
02
Relayer Observes + Fetches Proof
Relayer queries Taifoon for MMR proof of event inclusion
03
Proof Transport
Relayer submits message + proof to destination chain
04
On-Chain Verification
Destination contract verifies proof against Taifoon SuperRoot — trustless
Integration Pattern
Add Taifoon proof verification to your relayer system:
// Relayer observes event on source chain
const event = await sourceChain.getEvent(txHash);
// Fetch Taifoon proof
const proof = await taifoonAPI.getProof({
chain: 'ethereum',
txHash: txHash,
eventIndex: 0
});
// Submit to destination chain with proof
await destChain.executeMessage({
message: event.data,
proof: proof.mmrProof,
blockHeader: proof.header
});
// Destination contract verifies on-chain
function executeMessage(bytes calldata message, bytes calldata proof) {
require(taifoonVerifier.verify(proof), "Invalid proof");
// Execute message with cryptographic certainty
}KEY BENEFIT
Relayers no longer need to be trusted. Any party can verify message delivery by checking proofs against Taifoon's on-chain SuperRoot. This transforms relayers from trust assumptions into transport infrastructure.
Technical Specifications
| METRIC | VALUE |
|---|---|
| Proof Generation Time | < 500ms from finality |
| Proof Size | ~2.5 KB (constant across chains) |
| Verification Gas | ~21K gas (any EVM chain) |
| Supported Chains | 38 (EVM + Bitcoin, Solana, Polkadot, etc.) |
| Security Model | Cryptographic (no trusted parties) |
Next Steps