As developers, we're familiar with Proof of Work and Proof of Stake. Mezo, a Bitcoin L2, introduces a new variant: "Proof of HODL." Let's break down how this consensus mechanism works and what it means for dApp developers.
The Core Components:
Bitcoin L1: The settlement layer where user BTC is locked via a trust-minimized bridge (powered by tBTC, from the same team).
Mezo L2: An EVM-compatible execution layer where dApps live.
HODL Score: The key metric. It's a function of Amount of BTC deposited * Time Locked.
Validator Nodes: The operators who run the Mezo L2 blockchain.
The Consensus Flow:
User Deposits BTC: A user sends BTC to their "HODL Vault" on the Mezo L2. This locks the BTC on the L1. The user commits to a specific lock-up duration.
HODL Score is Calculated: The Protocol assigns the user a HODL score based on their deposit.
Delegation to Nodes: The user then delegates their HODL score to a validator Node of their choice. This is similar to delegating your stake in a traditional PoS system.
Consensus Weight: The validator's weight in consensus (their probability of proposing a new block) is proportional to the total HODL score delegated to them.
Earning Rewards: Both the user and the validator they delegate to earn Rewards from transaction fees and protocol incentives. Longer lock-up periods result in a higher share of rewards.
For a dApp developer, this means you are building on a network secured by the long-term conviction of Bitcoin holders. The underlying Staking asset is not a volatile new token, but Bitcoin itself.
For a deeper architectural breakdown and to prepare for the mainnet, the official community documentation is the most comprehensive Guide available.
Top comments (0)