Bridge In to Mezo
From Bitcoin to Mezo
1
Lock BTC
Lock BTC to the bridge-controlled address with metadata identifying the Mezo recipient.
2
Submit Proof
Submit proof and attestation to Mezo Bridge contract.
3
Verify Proof
Contract verifies proof.
4
Mint Asset
Mint corresponding asset on Mezo to recipient.
From Ethereum to Mezo
1
Lock ERC-20
Lock the ERC-20 on Ethereum via the Mezo Bridge contract, emitting an
AssetLocked event with Mezo recipient.2
Validators Listen
Bridge validators listen for such events.
3
Validate Events
Bridge validators validate events inclusion and validator quorum.
4
Mint Asset
Mint corresponding asset on Mezo to recipient.
Bridge Out of Mezo
From Mezo to Bitcoin
1
Burn Asset
Burn the asset on Mezo specifying the Bitcoin recipient address.
2
Submit Proof
Submit proof and attestation to Mezo Bridge contract.
3
Verify Proof
Contract verifies proof.
4
Release BTC
Upon verification, BTC is released to the recipient address.
From Mezo to Ethereum
1
Burn Asset
Burn the asset on Mezo specifying the Ethereum recipient.
2
Validators Listen
Bridge validators listen for
AssetsUnlocked events.3
Validate Events
Bridge validators validate events inclusion and validator quorum.
4
Release ERC-20
Upon verification, the ERC-20 is released to the recipient.
Architecture
The Mezo Bridge architecture consists of three key components:
- Lock/Burn on Source: Assets are locked on Bitcoin/Ethereum (or burned on Mezo) with data that identifies the intended recipient and target chain.
- Attestation & Relay: Offchain clients produce attestations over source-chain events and relay proofs to the destination chain.
- Mint/Release on Destination: Upon valid attestation and proof verification, destination contracts mint wrapped assets or release locked funds.
Core Flow
1
Initiate Transfer
User initiates a bridge transfer specifying destination address and amount.
2
Emit Event
Source-chain contract/event is emitted after lock/burn; event includes unique sequence ID and parameters.
3
Submit Proof
Offchain client collects confirmations/finality per RFC thresholds and submit proof+attestation to destination contract.
4
Verify
Destination verifies:
- Event authenticity
- Validator quorum/signatures
5
Execute
On success, destination executes mint/release and records completion.
Smart Contracts
Mainnet
list
Sepolia Testnet
list