Merkle Root
Pronunciation: MUR-kul ROOT
Definition
A Merkle root is the final hash at the top of a Merkle tree. It acts as a compact commitment to a collection of data, provided the underlying hashing and encoding rules are followed.
Overview
What it means and why it exists
A Merkle root is the final hash at the top of a Merkle tree. It acts as a compact commitment to a collection of data, provided the underlying hashing and encoding rules are followed.
How it works
A blockchain block can store a Merkle root in its header. To check whether a transaction is among that block's transactions, a verifier combines the transaction's hash with a sequence of sibling hashes and compares the computed result with the header value. Altering included data will ordinarily change the commitment.
Technical details worth understanding
For Bitcoin, the block's transaction Merkle root commits to transaction IDs. Witness data is handled through SegWit's separate witness commitment, which avoids confusing txid with wtxid. Account-based chains may use transaction, receipt and state roots with distinct meanings. A state root is not interchangeable with the root of transaction hashes.
What can go wrong
A root by itself does not prove that a block is canonical. A node still needs to verify consensus and chain selection, while merchants must check transaction status and specific payment details. A root also does not reveal all underlying transactions to a reader who lacks the data.
Practical checks
If an explorer says a transaction is included, identify the block header whose commitment supports that claim. A valid Merkle path to an old, reorganized block is still internally consistent but may no longer satisfy a merchant's confirmation policy. This is why header verification and canonical-chain tracking must accompany inclusion proofs.
Related concepts
Blockchain, Bitcoin (BTC), Transaction Hash.
Further reading
Example
A developer verifies a transaction proof against the root in a Bitcoin block header. Later, the block is orphaned by a chain reorganization. The original proof remains consistent with that old block, but it no longer supports the merchant's intended confirmation policy.
Comparison
A Merkle root summarizes data; a Merkle proof links one item to that root. A block hash identifies the block header as a whole, which includes more than the Merkle root.
Key Takeaway
For Bitcoin, the block's transaction Merkle root commits to transaction IDs.
Sources
- Ethereum Data Structures and Encoding — Ethereum Foundation (2026-08-01)