Hemi Network: How Logic-Driven Finality Works on Bitcoin's Newest $1B L2

In March 2025, Hemi Network launched its mainnet with $440 million in pre-deposited value on day one. Within months, self-reported TVL figures reached $1.2 billion, placing it among the largest Layer 2 networks claiming Bitcoin heritage. The pitch: an EVM-compatible chain that embeds Bitcoin's full state into smart contract execution, secured by publishing cryptographic proofs directly to Bitcoin's blockchain.

That pitch raises hard questions. Is Hemi genuinely a Bitcoin Layer 2, or an Ethereum rollup with a Bitcoin marketing wrapper? Do those TVL numbers hold up under scrutiny? And how does embedding Bitcoin state into an EVM actually work at a technical level? This article examines Hemi's architecture, security model, and growth trajectory with the rigor these questions deserve.

What Is Hemi Network

Hemi is a modular blockchain built on Optimism's OP Stack, making it structurally an optimistic rollup that posts transaction data to Ethereum (using EIP-4844 blobs) for data availability. On top of this Ethereum-native rollup architecture, Hemi layers Bitcoin security through its Proof-of-Proof (PoP) consensus mechanism: independent miners periodically publish Hemi state proofs into Bitcoin transactions, anchoring the chain's history to Bitcoin's proof-of-work.

This dual inheritance is what makes Hemi unusual. It claims to be both a Bitcoin L2 and an Ethereum L2 simultaneously: Ethereum provides data availability and the execution environment, while Bitcoin provides an additional finality layer. The team calls this combined guarantee "superfinality": once PoP proofs receive six Bitcoin block confirmations (roughly 60 minutes), reorganizing Hemi's state would require 51% attacking both Bitcoin and Hemi simultaneously.

Hemi was founded by Jeff Garzik, a former Bitcoin Core developer who worked alongside Satoshi Nakamoto in Bitcoin's earliest years and spent a decade at Red Hat on the Linux kernel, alongside Maxwell Sanchez, who previously developed the Proof-of-Proof mechanism at VeriBlock. The project has raised $30 million across two rounds led by Binance Labs (now YZi Labs), Breyer Capital, and Republic Digital.

How Proof-of-Proof Consensus Works

The Proof-of-Proof mechanism is Hemi's primary differentiator from standard OP Stack rollups. PoP miners are independent participants who periodically take Hemi block headers, compress them into compact proofs, and embed those proofs in Bitcoin transactions. This creates an immutable record of Hemi's state history within Bitcoin's blockchain.

The Node Architecture

Hemi runs five specialized node types, each handling a distinct role in the consensus and execution pipeline:

• Bitcoin-Secure Sequencer (BSS): constructs Hemi blocks by combining transactions from the mempool, Ethereum mainnet data, and new Bitcoin headers
• Bitcoin Finality Governor (BFG): monitors Bitcoin for PoP transactions, determines when Hemi blocks have achieved Bitcoin-level finality, and serves as the checkpoint mechanism
• PoP Miners: independent participants who publish Hemi state proofs into Bitcoin transactions, anchoring the chain's history to Bitcoin's proof-of-work
• Challengers: monitor and verify correctness of state transitions and proofs
• Modified Geth Node: manages Ethereum transaction processing and block header ingestion for Hemi's bridging protocols

PoP vs. merged mining: Unlike sidechain approaches such as Rootstock that rely on merged mining (requiring Bitcoin miner participation), PoP miners operate independently. Any participant can publish proofs to Bitcoin without permission from or coordination with Bitcoin miners. This lowers the barrier to entry but shifts the security assumption: PoP security depends on having enough active PoP miners publishing proofs, rather than inheriting hash rate directly.

The Finality Timeline

Hemi's finality model operates on multiple time horizons. Transactions reach soft confirmation within seconds through the sequencer, Ethereum-level finality after the rollup batch is posted (minutes to hours depending on the challenge period), and "superfinality" after the corresponding PoP proof receives six Bitcoin confirmations (approximately 60 minutes). The team argues this layered approach provides stronger guarantees than either chain alone, since reversing a superfinalized block would require simultaneously reorganizing both Bitcoin and Ethereum.

The Hemi Virtual Machine and Bitcoin State Access

The hVM (Hemi Virtual Machine) extends the standard EVM with native Bitcoin awareness. At its core sits Tiny Bitcoin (TBC), a full Bitcoin node daemon embedded within the EVM state machine. TBC synchronizes with the Bitcoin network via P2P connections, indexes Bitcoin blocks up to the protocol-specified height, and produces a "Processed Bitcoin View" that is synchronized across all Hemi nodes as part of the EVM state transition.

This means every Hemi node maintains an identical, deterministic view of Bitcoin's state. Smart contracts can query this view through custom precompile contracts: special EVM opcodes that fetch data directly from the Processed Bitcoin View. A developer deploying a DeFi protocol on Hemi can write Solidity code that reads Bitcoin UTXO data, verifies block headers, or checks transaction confirmations without relying on external oracles.

The Hemi Bitcoin Kit (hBK) wraps these low-level precompiles into a developer-friendly toolkit. In theory, this enables use cases like trustless Bitcoin-collateralized lending, automated cross-chain settlement triggered by Bitcoin confirmations, and DeFi protocols that react to on-chain Bitcoin events without intermediaries.

The oracle elimination pitch: Most EVM chains that interact with Bitcoin rely on oracles (Chainlink, Pyth) to feed Bitcoin data into smart contracts. Hemi's hVM eliminates this dependency for Bitcoin-specific data by making the EVM itself Bitcoin-aware. This reduces one attack surface (oracle manipulation) but introduces another: the correctness of the TBC daemon and its synchronization with Bitcoin's canonical chain.

Bitcoin Tunneling: Bridge Mechanics and Trust Assumptions

Moving Bitcoin into and out of Hemi uses a mechanism called "tunneling" rather than traditional bridging. For deposits, users send BTC to a custodial vault address. After six Bitcoin confirmations (approximately one hour), representative tokens are minted on Hemi. For withdrawals, users burn representative tokens, triggering a state root update submitted to Bitcoin. The custodial vault releases BTC after verification, which Hemi documentation states may take up to 12 hours.

The current implementation relies on multisig custodians to authorize withdrawals, with the hVM monitoring for irregularities. Hemi's roadmap describes plans to adopt an adapted version of BitVM2 for trust-minimized Bitcoin bridge verification, but this is not yet implemented. Until it is, the bridge's security depends on the honesty of a permissioned set of custodians: a significant trust assumption that users should understand before depositing funds.

How Hemi Compares to Other EVM-on-Bitcoin Approaches

Hemi enters a crowded field of projects attempting to bring EVM programmability to Bitcoin. Each takes a fundamentally different approach to the core challenge: how do you inherit Bitcoin's security while running an execution environment Bitcoin was never designed for? Here is how they compare across the dimensions that matter most.

Rootstock has the longest track record (operational since 2018) and the strongest direct Bitcoin security through merged mining, but has struggled to attract significant DeFi activity despite years of availability. BOB and Citrea take more novel approaches to Bitcoin data availability. Merlin Chain attracted substantial TVL in early 2024 through incentive programs but faced questions about bridge security and TVL sustainability: a pattern worth watching across the sector.

TVL Growth: Incentives vs. Organic Demand

Hemi's TVL narrative requires careful examination. The project launched mainnet on March 12, 2025, reporting $440 million in TVL on day one. By late 2025, some sources cited figures above $1.2 billion. But independent trackers tell a very different story.

L2BEAT, which measures only canonically bridged value, lists Hemi's Total Value Secured at approximately $1 million. DefiLlama shows DeFi TVL in the single-digit millions. The gap between self-reported and independently verified figures likely reflects different measurement methodologies: pre-deposited and committed capital, staking commitments, and assets not yet bridged on-chain may all contribute to the higher number.

This discrepancy is not unique to Hemi. Across the Bitcoin L2 landscape, TVL figures have been consistently inflated by point programs, pre-deposit campaigns, and double-counting of bridged assets. The more useful question is whether real economic activity exists on the chain: active DeFi protocols, meaningful transaction volume, and developers building applications that use Hemi's unique capabilities (particularly the hVM's Bitcoin state access).

What Drove the Growth

Several mechanisms contributed to Hemi's early deposits:

• A testnet points program that attracted over 200,000 PoP miners and 914,000 wallets, with points converting to HEMI tokens at the August 2025 Token Generation Event
• A Binance Wallet Booster campaign allocating 200 million HEMI tokens (2% of total supply) to early participants
• Partnerships with 50+ protocols at launch, including Sushi, DODO, LayerBank, ZeroLend, RedStone, Pyth, and LayerZero
• Institutional commitments (BTCS S.A. pledged 50 to 100 BTC)

The HEMI token launched on August 29, 2025, with a total supply of 10 billion tokens. It serves as the network's gas token, governance instrument (lockable as veHEMI for voting), and PoP miner reward. Token price declined significantly from its all-time high of approximately $0.19 in September 2025, reflecting broader market dynamics and post-airdrop selling pressure common across the L2 sector.

Security Model: What L2BEAT Says

L2BEAT provides the most rigorous independent assessment of L2 security, and their evaluation of Hemi is sobering. As of this writing, Hemi is classified below Stage 0: their lowest tier, indicating that the "proof system isn't fully functional."

These are not unusual findings for a young L2. Most OP Stack rollups launch with training wheels: centralized sequencers, permissioned proposers, and upgradeable contracts. The critical question is whether these are temporary scaffolding on a credible path to decentralization, or permanent features obscured by marketing language. Hemi's roadmap includes fault proof implementation, sequencer decentralization, and the BitVM2-based bridge, but none are operational yet.

Zero-delay upgrades are a critical risk: A 3-of-8 multisig with no timelock means three compromised signers could instantly drain all bridged funds by upgrading the contract logic. Most mature L2s implement multi-day upgrade delays specifically to give users time to exit before malicious upgrades take effect. Users should factor this into their risk assessment.

The EVM-on-Bitcoin Question

Hemi exists within a broader debate about whether porting Ethereum's execution environment to Bitcoin creates genuine value or simply replicates existing DeFi primitives on a chain that doesn't need them. The criticism is pointed: launching the same AMMs, lending protocols, and yield farms that already exist on Ethereum, Arbitrum, and Base onto a Bitcoin-branded chain has historically not attracted lasting liquidity.

Rootstock demonstrated this over eight years. Despite full EVM compatibility and strong Bitcoin security through merged mining, its DeFi ecosystem never reached the scale of Ethereum L2s. The liquidity simply didn't migrate. Merlin Chain showed the opposite extreme: massive TVL fueled by incentives that evaporated when rewards dried up.

Hemi's counterargument centers on the hVM. If smart contracts can natively read Bitcoin state without oracles, entirely new application categories become possible: trustless Bitcoin-collateralized lending where the collateral is verified on-chain rather than through custodians, automated settlement triggered by Bitcoin confirmations, and DeFi protocols that react to Bitcoin network events in real time. Whether developers actually build these Bitcoin-native applications, or simply deploy forks of existing Ethereum protocols, will determine whether Hemi's technical differentiation translates into lasting adoption.

Where Hemi Fits in the Bitcoin L2 Design Space

The Bitcoin Layer 2 landscape spans a wide spectrum of design philosophies. At one end sit EVM-compatible chains like Hemi, Rootstock, and BOB that prioritize developer familiarity and DeFi composability by adopting Ethereum's execution model. At the other end sit protocols that build directly on Bitcoin's native primitives.

Spark, for example, takes a fundamentally different approach. Rather than porting an EVM to Bitcoin, Spark uses statechains and FROST threshold signatures to enable instant, self-custodial Bitcoin transfers without broadcasting on-chain transactions. There is no virtual machine, no smart contract language, and no need to bridge Bitcoin into a separate execution environment. Transfers happen by rotating key ownership rather than executing EVM bytecode.

These represent genuinely different bets on what Bitcoin scaling should look like. Hemi bets that Bitcoin needs Ethereum's programmability: that DeFi, NFTs, and complex smart contracts are valuable enough to justify the additional trust assumptions of an EVM rollup. Spark bets that Bitcoin's primary scaling need is efficient value transfer: instant payments and dollar-denominated balances with minimal trust assumptions and no execution environment overhead.

For developers evaluating the design space, the choice depends on what you're building. If you need Solidity smart contracts that interact with Bitcoin state, Hemi's hVM is purpose-built for that use case. If you need instant, low-cost Bitcoin and stablecoin transfers with self-custody guarantees, the Spark SDK provides a simpler integration path. Understanding both architectures helps clarify what tradeoffs each makes and which fits your application.

What to Watch

Hemi's long-term viability hinges on several open questions:

• Fault proof deployment: until operational, the chain cannot offer meaningful security guarantees beyond trusting the centralized proposer
• BitVM2 bridge implementation: the current multisig custodial bridge is the weakest link in the security model
• Upgrade timelock: adding meaningful delay to the 3-of-8 multisig upgrade mechanism is necessary for user protection
• Developer adoption of hVM: whether applications leverage Bitcoin-native precompiles or simply deploy standard Ethereum DeFi forks will determine if Hemi's technical differentiation matters
• TVL quality: whether real economic activity and organic demand replace incentive-driven deposits as point programs wind down

Hemi represents an ambitious attempt to merge Bitcoin's security with Ethereum's programmability. The embedded Bitcoin node within the EVM is a genuinely novel technical contribution. But novel architecture alone does not guarantee adoption, and the current security posture (no fault proofs, centralized roles, zero-delay upgrades, custodial bridge) means users are placing significant trust in the team and its multisig signers. As the Bitcoin L2 ecosystem matures, the projects that thrive will be those that deliver on decentralization roadmaps rather than just announcing them.

For a broader comparison of approaches across the Bitcoin scaling landscape, see our Bitcoin second-layer scaling landscape overview and the BtcFi landscape analysis.

This article is for educational purposes only. It does not constitute financial or investment advice. Bitcoin and Layer 2 protocols involve technical and financial risk. Always do your own research and understand the tradeoffs before using any protocol.