Utreexo

Definition: Utreexo is a dynamic hash-based accumulator design for representing Bitcoin’s current set of unspent transaction outputs (UTXOs) with a compact Merkle-forest state. A compatible node can check an input’s membership using a proof instead of storing every UTXO record locally, trading lower local storage for extra proof data and network coordination.1 BIP 181 remains a draft for the accumulator itself; it does not specify integration into Bitcoin’s consensus or peer-to-peer protocols, so Utreexo is not an activated Bitcoin consensus feature.2

Date created Proposed for Bitcoin’s UTXO set in a research paper published in 2019.1
Protocol specification BIP 181 Draft
Implementation reference Utreexo accumulator library3
Directories Bitcoin Technology & Infrastructure

In-Depth Explanation

Why represent the UTXO set more compactly?

Bitcoin transactions spend earlier outputs and create new ones. To validate a spend, a node needs to know that each referenced output exists, remains unspent, and can be spent under the applicable script rules. Ordinary Bitcoin node software keeps a local database of the current UTXO set so it can perform these checks. That database is only the set of outputs not yet spent; it is not the entire transaction history. As the set grows, maintaining it adds storage and hardware requirements for node operators.1

Utreexo explores a different representation: keep a compact commitment to the set, then use cryptographic membership proofs when a node needs to check a particular UTXO. The goal is to reduce the persistent data a validating node must store, while retaining the ability to check relevant transaction data and rules when the required proofs are available. This describes a research design, not the default behavior of Bitcoin Core.1

How the accumulator and proofs work

Utreexo uses a dynamic forest of Merkle trees. The UTXOs are represented as leaves; hashes are combined up each tree to form roots that commit to the represented set. A membership proof supplies the hashes along a path so a node can recompute the relevant root and check that a claimed output is included. The BIP 181 draft specifies accumulator operations and proof generation and verification, including updates as elements are added or deleted.2

This connects Utreexo to a Merkle tree and a Merkle proof, but the accumulator is designed for a set that changes as Bitcoin outputs are created and spent. A proof shows membership relative to a particular accumulator state. By itself, it does not establish that the state was correctly derived from Bitcoin’s valid history; an implementation also needs a way to authenticate the commitment and keep proofs current.

Storage and bandwidth trade-offs

A smaller local state shifts some work to the network. A node may need proof data when it receives a transaction or block, and proofs must be updated as the accumulator changes. The original 2019 paper’s bandwidth estimate came from a simulation of downloading the Bitcoin chain only through early 2019, with 500 MB allocated for caching; it is not a current measurement of today’s network or implementations.1 Actual costs depend on the integration, proof format, caching, and how proof data is served.

In the current utreexod implementation, a bridge node keeps the full Merkle forest and attaches proofs to blocks and transactions for Utreexo nodes. That project reports higher bandwidth than a conventional node, as well as beta status and a warning against using its mainnet implementation for more than negligible bitcoin amounts. Those statements describe utreexod, not all possible Utreexo designs.4

How it differs from SPV

Simplified Payment Verification (SPV) uses block headers and transaction-inclusion proofs to check that a transaction appears in a block, but does not independently validate every transaction and consensus rule as a full node does. Utreexo’s research goal is different: let a node represent the UTXO state compactly and check input membership with proofs. The 2019 paper describes that as a route toward lightweight nodes that can perform full-node validation, but BIP 181 leaves Bitcoin protocol integration to future work.12

Development and limitations

Utreexo is not a switch that current Bitcoin Core users can turn on. BIP 181 is marked Draft and defines the accumulator rather than how it would be used in Bitcoin’s validation and peer-to-peer protocols.2 The separate utreexod project implements a Bitcoin node with Utreexo support and describes itself as under active development in beta; its project-specific warning says not to use mainnet for meaningful amounts of bitcoin.4 Treat the accumulator specification, any protocol integration, and each implementation’s readiness as separate questions.

History

  • 2019: Thaddeus Dryja published the Utreexo research paper proposing a hash-based accumulator optimized for Bitcoin’s UTXO set.1
  • June 18, 2025: BIP 181 was created as a draft specification for Utreexo’s accumulator operations and inclusion proofs; Bitcoin protocol integration is outside its scope.2
  • As of November 12, 2026: the separate utreexod project describes its node as beta and advises against using it on mainnet for meaningful amounts.4

Last updated: November 12, 2026.

Related Terms

Related Articles

No current CryptoGloss article focuses on Utreexo. These broader articles cover adjacent Bitcoin incentives, proof systems, network trust, and storage trade-offs; the zero-knowledge article discusses a different proof family from Utreexo’s Merkle inclusion proofs.

See Also

Sources

  1. Thaddeus Dryja, “Utreexo: A Dynamic Hash-Based Accumulator Optimized for the Bitcoin UTXO Set,” Cryptology ePrint Archive, Report 2019/611 (2019), https://eprint.iacr.org/2019/611 (accessed November 12, 2026).
  2. Thaddeus Dryja, Calvin Kim, and Davidson Souza, “BIP 181: Utreexo Accumulator Specification,” Bitcoin Improvement Proposals, created June 18, 2025, status Draft, https://github.com/utreexo/biptreexo/blob/main/bip-0181.md (accessed November 12, 2026).
  3. Utreexo contributors, “Utreexo: A Hash-Based Dynamic Accumulator,” GitHub repository README, https://github.com/utreexo/utreexo (accessed November 12, 2026).
  4. Utreexo contributors, “utreexod,” GitHub repository README, https://github.com/utreexo/utreexod (accessed November 12, 2026).