Taifoon 2026: The Proof Roadmap

Written March 2026. Parts of this plan have since moved. The current plan, with what is live and what is proposed, is at taifoon.io/roadmap.

SYSTEM STATE: Q1 2026

1PROCESS:   Spinner (Rust, 30+ crates)
2STATE:     RUNNING
3CHAINS:    41 active (EVM × 28, Solana, BTC, ICP, Aptos, Polkadot, TRON, SUI)
4BLOCKS:    2,700,000+ collected, indexed, verified
5MMR:       Live — O(log n) inclusion proofs
6DA API:    api.taifoon.dev — proof generation < 20ms
7INFRA:     K8s cluster, 99.9% uptime target

This is the baseline. Forty-one chains. One Merkle Mountain Range per chain. Every block header collected, every proof answerable.

The collection layer is done. The proof layer is live. What follows is the execution layer, the part where cross-chain state becomes programmable.

Q1 to Q2 2026: Lambda + SURGE Activation

The Lambda State Machine

Cross-chain execution requires more than proof generation. It requires a state machine that can:

1. Accept a cross-chain order from any supported chain
2. Verify the triggering event against the MMR root (on-chain, no trusted party)
3. Route execution to the optimal network via SURGE
4. Settle and attest finality back to the origin chain

This is Lambda. It is not a bridge. It carries no custody. It coordinates execution through verified state, with MMR proofs as the coordination primitive.

1ORDER SUBMITTED ──▶ MMR VERIFY ──▶ SURGE ROUTE ──▶ EXECUTE ──▶ ATTEST
2        │                │                │              │           │
3   any chain         on-chain        optimal path    destination   origin
4   (EVM/SVM/ICP)   TaifoonVerifier   (gas + liquidity) settlement  confirmation

SURGE Execution Layer

SURGE is Taifoon’s execution routing engine. When a Lambda order is verified, SURGE selects the execution path based on:

• Real-time gas oracle data (all 41 chains, sub-second updates)
• Liquidity depth per DEX adapter (Uniswap V3, custom executor adapters)
• MEV exposure and slippage bounds
• Bridge cost vs. native settlement cost

The result is deterministic cross-chain execution that anyone can verify.

Target Q2 milestone: First live Lambda execution: cross-chain settlement with a full MMR proof trail, publicly verifiable.

Q3 2026: SDK + Builder Ecosystem + Incubator

Proofs over HTTP

Any developer building cross-chain applications can use Taifoon’s proof layer directly. There is no SDK to install: the proof is one call.

1// Fetch the V5 proof for a block on any chain in the record
2const proof = await fetch(
3  'https://api.taifoon.dev/api/v5/proof/blob/1/21847003',
4).then((r) => r.json());

The proof API returns everything needed for on-chain verification in a single call. No custom indexer. No trusted relayer. One endpoint, one call, one verifiable result.

Ideal Customer Profiles

1ICP 01 — BUILDERS
2─────────────────────────────────────────────────────────
3Who:      Solidity/Rust developers, cross-chain protocol
4          teams, bridge architects, L2 settlement layers
5Need:     Trustless proof of cross-chain events without
6          running their own indexer or oracle committee
7Get:      one HTTP call → verifiable inclusion proof
8Path:     api.taifoon.dev/api/v5/proof/blob/:chain/:block
9Signal:   "We need to verify Ethereum state on Arbitrum"
10─────────────────────────────────────────────────────────
11
12ICP 02 — INFRASTRUCTURE
13─────────────────────────────────────────────────────────
14Who:      RPC operators, relayer networks, DA layer
15          providers, institutional blockchain data clients
16Need:     Real-time gas oracle, block attestation,
17          multi-chain MMR root subscriptions
18Get:      Production-grade API with SLA, verifiable roots
19Path:     Enterprise API tier → priority
20Signal:   "We need provable block headers at sub-second"
21─────────────────────────────────────────────────────────
22
23ICP 03 — MARKETS
24─────────────────────────────────────────────────────────
25Who:      Traders, whale signal consumers, MEV researchers,
26          DeFi analytics platforms, on-chain intel tools
27Need:     Live cross-chain signals, gas data, provable
28          large transfer events with entity attribution
29Get:      Signal stream, gas matrix, Arkham enrichment
30Path:     Telegram group → signal bot → API integration
31Signal:   "We need real-time provable cross-chain flows"
32─────────────────────────────────────────────────────────

Each ICP maps to a separate onboarding track. Builders get SDK docs and a sandbox. Infrastructure gets SLA-bound API keys. Markets get Telegram signal access and the gas oracle dashboard.

Q4 2026: MMR Cluster + Universal Settlement

MMR Cluster Formation

Phase six of the system unifies multiple independent MMRs, one per chain, under a cluster consensus root.

1CHAIN A MMR root ──┐
2CHAIN B MMR root ──┼──▶ CLUSTER CONSENSUS ROOT ──▶ AGGREGATED PROOF
3CHAIN C MMR root ──┘         (on-chain)
4       ...

A cluster root is a single cryptographic commitment to the state of all supported chains at a given moment. Any cross-chain proof can be verified against this root, without querying individual chain MMRs.

This removes the last latency bottleneck: instead of generating per-chain proofs independently, downstream systems receive a single attestation covering all chains simultaneously.

Universal Settlement Layer

With the cluster root live, Taifoon becomes a universal settlement primitive:

• Any contract on any supported chain can verify any cross-chain event
• A single proof format covers all chains (V5 proof specification)
• Any executor network can settle against one verifier address
• Cross-chain finality time: target < 5 seconds from event to proof availability

This is the terminal state of the roadmap: a system invariant.

THE INVARIANT

Every phase of this roadmap is a step toward a single guarantee:

Any event on any chain can be proven to any other chain, without trusting any intermediary.

That guarantee does not depend on committee size, liquidity depth, or token price. It depends on mathematics, specifically on the properties of append-only accumulators and Merkle inclusion proofs.

The Spinner collects. The MMR accumulates. Lambda coordinates. SURGE executes.

The system is deterministic. The proofs are portable. The settlement needs no trusted party.

ACCESS POINTS

1Scanner          api.taifoon.dev     real-time chain view
2Proof API        api.taifoon.dev         MMR proof generation
3Community        t.me/taifoon_intel_bot  signal + support
4Builders         t.me/taifoon_network/14     technical channel
5CLI              npm i -g @taifoon/cli