Merlin’s Seal (Merlin Chain)

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

REJECTED ON A THINNER APPROVAL SET THAN EVERY COMPARABLE BITCOIN WRAPPER ALREADY REJECTED IN THIS REGISTRY. Merlin’s Seal is the BTC-locking bridge for Merlin Chain, a Bitcoin Layer 2, using MPC custody co-managed by Cobo and Merlin Chain that requires both parties’ signatures to release funds. That two-party gate is smaller than WBTC’s 2-of-3 multisig or Function FBTC’s three-party Security Council, both already rejected in this registry for their own custody-concentration reasons, and current redemption mechanics for ordinary, non-promotional bridge transactions could not be confirmed from primary sources.

Kill criteria: the events that revoke this verdict
• The MPC custody threshold expands beyond a two-party gate to a broader, named signer set, or an independent third-party verifier is added to the release process
• Current redemption mechanism, timing, and any size limits for ordinary bridge transactions are independently confirmed and demonstrated at proposed size
• An independent, recurring proof-of-reserves attestation for MBTC and other Seal-bridged assets is published
• Twelve consecutive months with no depeg, custody, or bridge-release incident following threshold and redemption confirmation

The research file

Mechanism

Users deposit BTC, ETH, USDT, USDC, or BRC-20/BRC-420 tokens into an MPC wallet co-managed by Cobo and Merlin Chain. On Ethereum, BTC is locked and a message triggers minting of MBTC on Merlin’s L2 at a 1:1 ratio; reversing the flow burns MBTC and releases the locked BTC. Merlin’s Seal originated as a time-boxed 2024 token-launch event, but the underlying BTC-locking mechanism remains the live bridge path this entry evaluates.

Control and governance

Custody uses Cobo’s MPC and threshold-signature-scheme technology, requiring signatures from both Merlin and Cobo to release funds — a two-party approval structure, not a broad multisig or decentralized validator set. MPC avoids a single-key failure mode, but a two-party gate is thinner than WBTC’s 2-of-3 or FBTC’s three-party council, both already rejected in this registry for their own concentration reasons. A May 2026 upgrade added zkEVM scalability and BitVM-based Bitcoin-native security, and a proof-of-stake transition planned for 2026 aims to decentralize network operation — neither change affects the bridge’s own two-party custody gate.

Incident record

No confirmed exploit of Merlin Chain’s own BTC bridge or custody mechanism was identified through this review’s 2026-08-17 search cutoff. A widely-indexed ”Merlin DEX hack” from April 2023 belongs to an unrelated zkSync-based DEX that happens to share the Merlin name, not Merlin Chain; it is noted here only to prevent miscitation. Merlin Chain’s mainnet reportedly passed a CertiK audit with no critical findings before launch, and the team publishes audit reports and runs a bug bounty, but no dedicated audit of the Seal bridge’s custody mechanism specifically was confirmed.

Exit

Original Seal-era deposits were represented by non-transferable M-Tokens redeemable starting in an announced 2024 unlock window. Ongoing bridge redemption burns MBTC for locked BTC through the same two-party MPC release gate, but this review could not confirm current redemption timing or size limits for an ordinary, non-Seal-era bridge transaction from any primary source, nor whether the two-party approval could be unilaterally withheld by either Cobo or Merlin.

Comparison

Against WBTC (2-of-3 multisig, rejected for custody concentration) and Function FBTC (three-party council, rejected for an unconfirmed threshold), Merlin’s Seal’s two-party MPC gate is a smaller approval set than either. Against SolvBTC, rejected despite the strongest governance in this batch due to a realized exploit, and Lorenzo enzoBTC, rejected on unresolved disclosure gaps, Merlin’s Seal sits closest to enzoBTC: a plausible design with real open questions rather than a confirmed failure, but open questions are not a basis for allocation either.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• DefiLlama — Merlin’s Seal protocol record · secondary · accessed 2026-08-17
  Supports: tracked TVL
• Merlin Chain — official bridge and staking page · primary · accessed 2026-08-17
  Supports: mechanism
• Cobo — Cobo and Bitmap Tech establish Merlin Chain with MPC custody · primary · accessed 2026-08-17
  Supports: two-party MPC custody structure
• Messari — understanding Merlin Chain · secondary · accessed 2026-08-17
  Supports: protocol overview
• Xverse — what is Merlin Chain, a guide to the native Bitcoin Layer 2 · secondary · accessed 2026-08-17
  Supports: architecture summary

Inherited controls

The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.