Hemi (HEMI): What Does Bitcoin Actually Secure?

A record with a particular job

Hemi reached mainnet on March 12, 2025. Founded by early Bitcoin developer Jeff Garzik and Max Sanchez, the project describes Bitcoin and Ethereum as parts of a “supernetwork.” That term becomes more useful when broken into concrete jobs. Hemi runs an Ethereum-compatible execution environment; its Hemi Virtual Machine, or hVM, lets contracts on Hemi query Bitcoin data. Proof-of-Proof, or PoP, sends a record in the other direction: information about Hemi’s chain is published to Bitcoin. The question is what that publication can establish.^[1][2][8]

For readers who first heard of Hemi through Upbit, the September 8, 2026 notice needs a correction to the original listing headlines. HEMI trading against BTC and USDT was announced for 21:30 KST, but the exchange canceled it in a 21:12 update after identifying signs of token theft related to a security vulnerability. The planned opening did not go ahead. That episode is a reason to examine the meaning of Bitcoin-backed security carefully, rather than treat the phrase as a guarantee covering every part of Hemi.^[3]

What fits inside the Bitcoin transaction

The public implementation gives a remarkably small answer to “what is written?” In the code revision inspected for this article, the PoP payload starts with the four bytes spelling HEMI and adds a 76-byte abbreviated keystone. A keystone is a checkpoint used to refer to part of Hemi’s chain. The code places this payload after OP_RETURN, a Bitcoin script instruction used to carry data in an unspendable output. The 80 bytes are the payload, not the size of the entire Bitcoin transaction.^[4][5]

Those 76 bytes contain a version, L1 and L2 block numbers, shortened references to other block data, and a full 32-byte state root. The state root is a cryptographic commitment to a particular state: a compact value against which the underlying data can be checked. It is not that data itself. A useful analogy is filing a document’s fingerprint in a durable register while keeping the document elsewhere. The fingerprint helps identify the document; it does not contain all its pages or establish that every statement in them is correct.^[5]

A PoP miner obtains the checkpoint, builds the Bitcoin transaction and pays a fee in BTC to seek inclusion in a Bitcoin block. This is a different job from competing to produce Bitcoin blocks through proof of work. Ordinary Bitcoin miners can include the transaction under Bitcoin’s rules without running Hemi’s virtual machine. Once included, the publication becomes part of Bitcoin’s recorded history. Hemi software then has to recognize it and apply its own consensus rules; the Bitcoin transaction alone does not perform that second step.^[6][4]

How a record becomes part of fork resolution

Imagine two proposed Hemi histories that disagree about an earlier segment. In Hemi’s PoP design, the nodes resolving that disagreement use the publications in Bitcoin as external evidence. An alternative history cannot silently replace an already published checkpoint and still match the same record. The whitepaper links these publications to rules for choosing between forks and recognizing finality—the point at which the protocol treats a segment as settled. The security claim comes from those rules using Bitcoin’s history, not from attaching a hash to Bitcoin in isolation.^[6]

The whitepaper describes a nine-Bitcoin-block finality delay and a crucial condition: an actively mined competing fork must not be publishing to Bitcoin. If one is, the affected segment waits for the contest to be resolved. Even without a competing fork, Bitcoin block times and publication delays vary. Nine blocks is therefore not a guaranteed 90-minute service. The paper separately describes “superfinality” through the combined resistance of Bitcoin and Hemi’s native consensus. These are claims within the project’s security model, not an unconditional promise that any Hemi transaction is irreversible after a fixed wait.^[6][7]

The documentation also has a visible inconsistency: the finality page’s summary says superfinality arrives after six Bitcoin blocks, while its explanation applies a nine-block delay before ordinary finality. The whitepaper places superfinality after Bitcoin finality, so the page’s two numbers do not fit the same sequence. This article follows the whitepaper’s nine-block discussion when explaining the design, but does not certify that parameter across today’s mainnet. Hemi’s newer rollout materials still distinguish live features from forthcoming infrastructure. Reading an encoding function or a roadmap cannot establish which fork-choice rules, validator roles and settlement safeguards every deployed component currently enforces.^[7][13][14]

The checks that remain outside that record

The first remaining check is execution. Bitcoin validates the Bitcoin transaction containing the record; it does not replay Hemi’s EVM transactions to decide whether their resulting state is correct. Hemi’s hVM makes Bitcoin information readable by Hemi contracts, not the reverse. The whitepaper assigns transaction execution, data publication to Ethereum and challenges to incorrect state claims to separate parts of the system. A commitment to a result cannot replace those responsibilities.^[4][6][8]

An application can also follow its deployed code and still do something its developers never intended. Hemi’s September 8 post mortem says an attacker took about 124.5 million unclaimed HEMI from the legacy Genesis Drop contract the previous day. It attributes the loss to reentrancy: an external lockup call could re-enter the claim function before the remaining balance was updated. The team says the incident was confined to that claim contract and did not affect the HEMI or veHEMI tokens, hVM or tunnels. That is the team’s account, not an independent forensic finding. It illustrates why resisting a rewrite of history and preventing an application bug are different tasks.^[10]

The same boundary matters when moving BTC. Hemi’s Bitcoin Tunnel documentation describes BTC locked in custody vaults and representative tokens issued on Hemi. Returning BTC involves the applicable vault and authorization mechanism. A Bitcoin record of Hemi state does not itself possess a vault key or release those funds. The implementation and custody assumptions of the chosen route still matter, even when the chain history has a Bitcoin anchor.^[11]

Three assets, different jobs

The incentives have their own division of labor. A PoP publication consumes BTC for Bitcoin fees. HEMI is the token around which the project organizes incentives, staking and governance; its design includes rewarding PoP participation. Meanwhile, the mainnet connection documentation checked on October 7, 2026 lists ETH as the gas token. The whitepaper’s dual-asset fee model and the token page’s broader fee language should not be mistaken for proof that every current Hemi transaction is paid directly in HEMI. Likewise, the hemiStake materials separate live rewards from planned governance and infrastructure features.^{[6][9][12][14]}

Supply figures need the same care. The token page displays 10 billion HEMI, but also shows protocol emissions in its release schedule. An October 2026 project update describes 250 million HEMI in emissions over the following year. Reading the 10-billion figure as a permanently fixed maximum would therefore leave out part of the stated model. Neither an allocation nor an incentive schedule guarantees a return; here its relevance is how the network proposes to pay for participation.^[12][13]

Follow the guarantee to its boundary

PoP’s distinctive idea is to make Hemi’s history answer to a record published on another chain. The full path matters: a checkpoint is encoded, a Bitcoin transaction carries it, Bitcoin confirms it, and Hemi’s rules interpret it. That can support resistance to rewriting history under the stated model. Correct execution, available data, safe applications and the release of assets each require their own mechanisms. The most revealing question is therefore not simply whether Hemi uses Bitcoin, but which decision actually relies on that Bitcoin record—and which still has to be made elsewhere.^{[4][6][10][11]}