What is Merlin Chain?
👋 New to this? Just start reading at the top — it begins in plain English and gets more detailed as you scroll. Jump to any level:
🟢 The simple version
Plain English — no jargon. Start here.
Merlin Chain is a Bitcoin Layer 2 that uses ZK (zero-knowledge) proofs to run an EVM-compatible smart contract environment backed by Bitcoin — allowing Ordinals, BRC-20 tokens, Runes, and Solidity smart contracts to interact in a single execution environment with Bitcoin as the settlement layer.
Why a Bitcoin ZK rollup?
Ordinals and Runes created significant activity on Bitcoin but no programmability — you can't build a DEX or lending protocol directly with Ordinals inscriptions on Bitcoin mainchain. Ethereum L2s (Arbitrum, zkSync) proved that ZK proofs can extend a base chain with smart contracts without modifying it. Merlin Chain applies this logic to Bitcoin: take Bitcoin's existing assets (BTC, Ordinals, Runes, BRC-20), bring them into a ZK-rollup execution environment, enable DeFi applications, and settle proofs back to Bitcoin.
Merlin launched its mainnet in February 2024 and quickly accumulated significant TVL by targeting the Bitcoin-native asset community — users who held Ordinals and BRC-20 tokens but had no DeFi options for them.
How Merlin works
Users bridge Bitcoin assets (BTC, Ordinals, BRC-20, Runes) from Bitcoin mainchain into Merlin Chain through a bridge. On Merlin, these assets are represented as standard EVM tokens — wrapped BTC, Merlin-Ordinals, etc. Solidity developers can deploy contracts that interact with these assets. ZK proofs of Merlin's execution are generated and periodically committed to Bitcoin. The MERL token is the native gas token and governance token of Merlin Chain.
What MERL does
MERL is used for transaction fees on Merlin Chain, staking in Merlin's Proof of Stake validator set, and governance. Total supply: 2.1 billion MERL — matching Bitcoin's 21 million BTC × 100 (a deliberate homage).
Is it legal in India?
Yes. MERL is a VDA under Indian law. 30% tax and 1% TDS apply. See India regulation.
🟡 A bit more detail
For when you want to go a little deeper.
Merlin's Bitcoin asset bridge
Merlin's bridge handles multiple Bitcoin asset types simultaneously — a technical challenge because Ordinals, BRC-20, Runes, and BTC use fundamentally different data formats on Bitcoin. The bridge uses a multi-signature custody model (similar to Liquid Network's federation) where a set of validators collectively hold bridged Bitcoin assets. When a user bridges BTC to Merlin, the BTC is locked in the bridge multisig and MBTC (wrapped BTC) is minted on Merlin at 1:1. When bridging Ordinals, the specific inscription is locked and a corresponding ERC-721 token is minted on Merlin representing that specific inscription.
Merlin Chain became one of the largest Bitcoin L2s by TVL within months of launch, reaching over $1 billion in locked value by mid-2024. The primary activity: yield farming and lending with Bitcoin-native assets (BRC-20 tokens, wrapped BTC). Several DeFi protocols deployed on Merlin specifically to serve Bitcoin community users who held Ordinals and BRC-20 positions with no existing DeFi options. Merlin's growth demonstrated the demand for Bitcoin DeFi once Bitcoin-native assets became available to interact with programmatically.
ZK proof architecture
Merlin uses a ZK rollup model where transactions execute on an EVM and execution proofs are generated using ZK proof systems. The proofs attest that Merlin's state transitions are valid without requiring Bitcoin validators to re-execute every transaction. The proof commitments are periodically posted as Bitcoin transactions (using OP_RETURN or Taproot outputs), anchoring Merlin's state to Bitcoin's immutable record. This gives Merlin's state Bitcoin-level finality once the commitment is buried in Bitcoin blocks.
Key Merlin metrics: TVL (total value locked), daily active users, Solidity contracts deployed, ZK proof commitment frequency, and bridge security audits. Bridge security is the primary risk factor — a bridge exploit could drain locked Bitcoin assets. The centralisation of the bridge validator set is a known limitation compared to trustless alternatives. Live data: CoinGecko · Merlin Explorer.
🟣 The full technical picture
For the technically curious.
Merlin Chain technical stack
Merlin Chain is built on the Polygon CDK (Chain Development Kit) — the same modular ZK rollup framework used to build several Ethereum L2s. The CDK provides the EVM execution environment, ZK proof generation (using Polygon's Plonky2 or related proof systems), and state management. Merlin customised the CDK to support Bitcoin-native assets: the ERC-20 token contracts for wrapped BTC, BRC-20, and Runes are pre-deployed at specific contract addresses recognisable by the bridge.
Source: Merlin Chain documentation. docs.merlinchain.io · Merlin Chain: merlinchain.io
The native Bitcoin DeFi thesis
Merlin's design philosophy: Bitcoin has the largest holder base and the most trusted asset ($BTC) but the least DeFi infrastructure. Bitcoin-native assets (Ordinals, Runes, BRC-20) created a new class of assets with no DeFi options. An EVM L2 anchored to Bitcoin captures both Bitcoin's security brand and Ethereum's developer tooling, solving the programmability gap without requiring Ethereum bridges. The thesis is supported by Merlin's TVL growth — the demand was real once supply (a functional EVM environment) existed.
Merlin's Bitcoin inscription bridge requires special handling for Ordinals — unlike fungible tokens, Ordinals are non-fungible (each inscription is unique). When an Ordinal is bridged to Merlin, the bridge records the specific inscription ID (Bitcoin transaction ID + output index) and mints a corresponding ERC-721 token whose metadata references the inscription content. The bridge validator set must maintain a 1:1 mapping between locked inscription UTXOs and minted ERC-721 tokens. Bridge exploits would require compromising the multisig threshold — the primary security assumption that distinguishes Merlin from a fully trustless bridge model.
Key facts
- Type: Bitcoin L2 (ZK rollup, EVM-compatible)
- Mainnet: February 2024
- Tech stack: Polygon CDK (ZK proof framework)
- Assets supported: BTC, Ordinals, BRC-20, Runes
- MERL supply: 2.1 billion
- TVL peak: $1B+ (mid-2024)
- Bridge model: Multisig custody (threshold validators)