ICP-04MESSAGING & INTEROP
DUAL-PATH VERIFICATION
Add Taifoon as a trustless verification layer alongside your existing security stack. Your validators + our proofs = mathematical finality.
dual
Verification
trustless
Fallback
0
Validators Req.
finality
Guaranteed
HOW IT WORKS
Three steps to integration
01
Message Sent
Source chain emits a cross-chain message. Your existing validator set processes it normally.
02
Taifoon Proof in Parallel
Simultaneously, Taifoon generates an MMR inclusion proof for the source event. No added latency to your flow.
03
Dual Verification
Destination verifies both: your validators AND Taifoon's cryptographic proof. Mathematical finality, zero bridge trust.
START IN 4 MINUTES
Dual-path message verification
solidity~/quickstart.sol
1// SPDX-License-Identifier: MIT2pragma solidity ^0.8.20;34import {ITaifoonVerifier} from "@taifoon/contracts/ITaifoonVerifier.sol";56contract DualVerifyBridge {7 ITaifoonVerifier public taifoon;8 IValidatorSet public validators;910 function receiveMessage(11 bytes calldata msg_,12 bytes calldata validatorSigs,13 bytes calldata v5Proof14 ) external {15 // Path A: Your existing validator set16 require(validators.verify(msg_, validatorSigs));17 // Path B: Taifoon cryptographic proof18 (bool valid, ) = taifoon.verifyV5(19 srcChainId, v5Proof20 );21 require(valid, "Taifoon proof invalid");22 _processMessage(msg_);23 }24}WHO IT'S FOR
Potential integrators
AXELAR
Validator set model
LAYERZERO
ULN security stack
HYPERLANE
Modular security
WORMHOLE
Guardian network
CCIP
Oracle-backed relay
TRY IT
Generate a proof right now
Pick a chain, pick a block, get a V5 proof blob. Auto-hides if the API is unreachable.
