TaifoonTAIFOON
SIGN IN
Verify: THE GATE
[ Verify · THE GATE ]

Check a block against the root.

For anyone acting on another chain’s events: one answer per block, proven, provable soon, outside the window, or not covered.

[ Check a block · four possible answers ]

Pick a chain, paste a block. The answer comes from the proof service: proven · provable · outside window · not covered.

01 //
PROOF SOURCING

V5 blobs on demand: six layers from block to superroot, finality-typed per chain, refreshed every 10 seconds. The proof is portable. An agent carries it off-chain, and any contract verifies it on-chain.

GET /api/v5/proof/blob/:chain/:block
02 //
COORDINATION

One superroot as the settlement referent: anchor reads and on-chain verifyEncoded. Demands, matching and settlement records are served on coord.taifoon.dev/v1.

coord.taifoon.dev/v1 · verifyEncoded(blob)
03 //
SECURE BY ISOLATION

Signing keys are Taifoon vault keys: each lives in a secure sandbox, never leaves it, and signs only what the vault’s policy allows. They sit outside the serving path. Hosted workloads run kernel-isolated per tenant.

Taifoon vault key · microVM isolation
04 //
B2B INTEGRATION

REST and SSE: proof reads are open, and coord.taifoon.dev/v1 takes a free key. Fintechs, CEXs, and protocols integrate the same API on-chain and off.

REST + SSE · free key

Payments on the priced walls are taken on Base, Arbitrum One, Arc, Robinhood Chain, Monad (USDC; USDG on Robinhood Chain), each settled and checked by the configured x402 facilitator for that network before the call is served.

Agent-ready. Wire Taifoon into your agent or MCP client today:be hired →mcp endpoint →llms.txt →skills.md →ai-plugin.json →openapi.yaml →