ICP-04MESSAGING & INTEROP

DUAL-PATH VERIFICATION

Add Taifoon as a trustless verification layer alongside your existing security stack. Your validators + our proofs = mathematical finality.

INTEGRATE PROOFS →Dev Channel

dual

Verification

trustless

Fallback

Validators Req.

finality

Guaranteed

HOW IT WORKS

Three steps. We do the hard one.

Message Sent

Source chain emits a cross-chain message. Your existing validator set processes it normally.

Taifoon Proof in Parallel

Simultaneously, Taifoon generates an MMR inclusion proof for the source event. No added latency to your flow.

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: MIT
2pragma solidity ^0.8.20;
3
4// TaifoonV5ProofVerifier — LIVE on Base Sepolia (84532):
5//   0x8D4962d8bc69648F57D5cC4d68F073499b1f3293
6interface ITaifoonVerifier {
7    function verifyEncoded(bytes calldata blob) external returns (bool);
8}
9
10contract DualVerifyBridge {
11    ITaifoonVerifier constant TAIFOON =
12        ITaifoonVerifier(0x8D4962d8bc69648F57D5cC4d68F073499b1f3293);
13    IValidatorSet public validators;
14
15    function receiveMessage(
16        bytes calldata msg_,
17        bytes calldata validatorSigs,
18        bytes calldata v5Proof
19    ) external {
20        // Path A: Your existing validator set
21        require(validators.verify(msg_, validatorSigs));
22        // Path B: Taifoon cryptographic proof, verified on-chain
23        require(TAIFOON.verifyEncoded(v5Proof), "Taifoon proof invalid");
24        _processMessage(msg_);
25    }
26}