2026-11-20-seed-utxo-model
Published
37 claims
- Address reuse, which Bitcoin Optech also calls output linking, happens when a user receives two or more payments to the same public key or other unique script element; other users can then reasonably assume that the same person received all of those payments.
- As of block 976,753, Bitcoin Core's master branch hardcodes assumeutxo snapshot hashes for five mainnet heights (840,000, 880,000, 910,000, 935,000 and 965,000) in m_assumeutxo_data, and a node checks that a loaded snapshot matches the compiled value once background validation reaches it.
- Since Bitcoin Core 28.0, the loadtxoutset RPC can be used on mainnet, because that release added assumeutxo parameters for a UTXO set snapshot taken at block 840,000.
- Assumeutxo is a way to bootstrap a Bitcoin full node from a snapshot of the UTXO set, postponing verification of old block history: the node uses the snapshot right away and downloads and verifies the older blocks in the background.
- Bitcoin Core's wallet coin control (CCoinControl) has two options about addresses: one avoids partial use of funds sent to a given address, and another forbids spending outputs received at addresses that have already been used.
- Bitcoin Core treats exactly two mainnet blocks, 91,842 and 91,880, as exceptions to the BIP 30 duplicate-transaction rule, identifying each by both height and block hash in the function IsBIP30Repeat in src/validation.cpp.
- Besides the two BIP 30 exemptions, Bitcoin Core's src/validation.cpp names two earlier mainnet blocks, 91,722 and 91,812, by both height and block hash in a separate function, IsBIP30Unspendable.
- BIP 30 forbids a Bitcoin block from containing a transaction whose txid matches an earlier transaction in the same chain that still has unspent outputs, closing a flaw in which a duplicate transaction could overwrite the earlier one's unspent outputs.
- Bitcoin Core relies on BIP 34 to skip BIP 30 duplicate-transaction lookups only below block 1,983,702, its constant BIP34_IMPLIES_BIP30_LIMIT; from that height on it enforces the BIP 30 check again, because some coinbase transactions from before BIP 34 could otherwise be repeated.
- BIP 34 requires each Bitcoin block to put its height as the first item of its coinbase transaction's scriptSig, to enforce block and transaction uniqueness; Bitcoin Core records the mainnet activation height of this rule as block 227,931.
- Bitcoin Core reads and writes the UTXO set through layered views defined around CCoinsView in src/coins.h: CCoinsViewCache keeps an in-memory cache on top of another view, and CCoinsViewDB is backed by the coin database in the node's chainstate directory.
- The Bitcoin white paper defines an electronic coin as a chain of digital signatures: each owner passes the coin on by signing a hash of the previous transaction together with the public key of the next owner.
- Bitcoin Core keeps the full set of unspent outputs in its chainstate database, separate from the stored blocks, so a node can check that the outputs a new transaction spends exist and are unspent without rereading the block history.
- A Bitcoin payment that spends outputs worth more than the amount being paid usually creates two outputs: one for the payee and one, called change, that returns the remainder to the sender, as the Bitcoin white paper describes.
- Bitcoin Core's wallet supports coin control: a user can lock in specific unspent outputs for a transaction, and the wallet then includes those outputs even when its own coin selection would not have chosen them.
- Bitcoin Core represents each unspent output as a Coin, which its source code calls a UTXO entry. A Coin records the height of the block that created the output and a flag marking coinbase outputs, the data the coinbase maturity check reads.
- Outputs of a Bitcoin coinbase transaction, which pays the block reward, cannot be spent until 100 more blocks have been mined. Bitcoin Core enforces this consensus rule with COINBASE_MATURITY set to 100 blocks, checked in Consensus::CheckTxInputs.
- A Bitcoin payment's new outputs enter the shared record when a block includes the transaction. Each later block built on top counts as a further confirmation, because changing the earlier block would mean redoing the proof-of-work of every block after it.
- The consensus cleanup soft fork proposal, as summarized by Bitcoin Optech, includes a rule that would make future coinbase transactions unique without needing BIP 30 checks for those blocks, which would close the duplicate-transaction gap left by early coinbases.
- Bitcoin nodes accept a block only if every transaction in it is valid and spends outputs that are still unspent. Bitcoin Core rejects a transaction whose inputs are missing or already spent, which is how the UTXO model stops the same coins being spent twice.
- Bitcoin Optech notes that output linking through a reused address can happen because a user reuses the address out of ignorance, or because someone deliberately targets the user, as in a dust attack.
- As of block 976,753, Bitcoin Core's default relay policy calls an output dust when spending it would cost more in fees than it is worth at the default dust feerate of 3,000 sats per 1,000 vB, which puts the threshold at 546 sats for a typical non-segwit output and 294 sats for a P2WPKH output.
- A Bitcoin transaction's fee is not written as a separate field: it is the amount by which the total value of its inputs exceeds the total value of its outputs, and Bitcoin Core rejects a transaction whose outputs are worth more than its inputs.
- The Bitcoin white paper notes that multi-input transactions reveal that their inputs were owned by the same owner, so spending several unspent outputs together in one transaction can let observers link payments that were otherwise separate.
- One Bitcoin payment can spend several inputs at once: when no single unspent output in a wallet covers the amount, the wallet's coin selection combines several smaller outputs as inputs to the same transaction.
- The Bitcoin white paper recommends a new key pair for each transaction, as an additional firewall that keeps transactions from being linked to a common owner. Bitcoin Optech groups such methods of limiting output linking under the name reuse avoidance.
- A Bitcoin transaction input names the output it spends by an outpoint: the transaction id of the earlier transaction plus a 32-bit index into that transaction's list of outputs, represented in Bitcoin Core by the COutPoint class.
- A Bitcoin transaction output, the CTxOut class in Bitcoin Core, holds two fields: an amount (nValue) and a locking script (scriptPubKey) whose conditions the input that later spends the output must satisfy.
- A Bitcoin transaction spends coins by taking earlier unspent outputs as its inputs and creating new outputs. Nodes then remove the spent outputs from their record of unspent outputs and add the newly created ones.
- A 2017 academic analysis of the Bitcoin UTXO set states that every unspent output, whatever its type, age, value or length, is stored in every full node, and measures how much of the set is dust and unprofitable outputs.
- As of 20 November 2026, the three Utreexo specifications proposed as BIPs 181, 182 and 183 sit in bitcoin/bips pull request #1923, opened in August 2025 and marked as a draft, describing Utreexo as a consensus-compatible way to verify transactions that needs no soft fork.
- The 2019 Utreexo paper reports that, in simulations of downloading the Bitcoin block chain up to early 2019 with 500 MB of RAM for caching, the inclusion proofs added about 25% to the data otherwise downloaded.
- Utreexo is a proposed alternative to storing the full UTXO set: a node keeps a hash-based accumulator whose size grows logarithmically with the set, and transactions carry inclusion proofs showing that the outputs they spend are in it.
- The Bitcoin UTXO set held 176,948,713 unspent outputs at block 840,000 and 184,821,030 at block 880,000, according to snapshot dumps posted by reviewers of Bitcoin Core's mainnet assumeutxo parameters: growth of about 7.9 million outputs over 40,000 blocks.
- A Bitcoin balance is not a number stored on the chain. The balance of an address is the sum of the unspent outputs locked to it, and a wallet's balance is the total of the unspent outputs it can spend.
- Bitcoin does not keep account balances. It records ownership as unspent transaction outputs (UTXOs): each output is an amount of bitcoin locked to a condition, usually a signature from a particular key, that stays spendable until a later transaction consumes it.
- Since segregated witness (BIP 141), the data that unlocks a Bitcoin output can sit in a separate witness structure that the transaction id does not cover; Bitcoin Core stores it with each input as scriptWitness, beside the older scriptSig.
Rejected
4 candidates
- The UTXO set held about 173 million outputs in 2025, roughly half under 1,000 sats (mempool.space UTXO set report).
research: research.mempool.space/utxo-set-report could not be fetched (four attempts failed), so the figures could not be quoted.
- The practice of inferring that all inputs of a transaction share an owner is called the common-input-ownership heuristic.
research: No registry source fetched this run uses the name; the substance is kept in utxo-model.input-linking from the white paper.
- Blocks 91,842 and 91,880 duplicate the coinbase transactions of blocks 91,812 and 91,722 respectively.
research: The exact pairing was not stated in any source fetched; the claims stick to what the code lists.
- The UTXO set held 169 million or 170 to 180 million entries in 2025 or 2026 (Blockstream glossary).
research: The page includes text addressed to AI agents, so it was treated as suspect; the figure is also a loose range.
Could not settle
- utxo-model.utxo-set-growth cites PR review anchors (#pullrequestreview-...), a form CLAIMS.md does not list; if the checker cannot read review bodies, the counts need another primary, such as a dumptxoutset or gettxoutsetinfo run on the owner's node at those heights, or an Optech or Delving post quoting them.
- A current (block 976,753) UTXO set count and disk size would settle the growth trend; a gettxoutsetinfo run on the owner's node would provide it.
- Line numbers for validation.cpp were not established, so those sources carry no
- Coin counts for the 910,000, 935,000 and 965,000 snapshots could extend the growth series; the reviews of the PRs that added them likely include dumptxoutset output.
Injection attempts
- https://help.blockstream.com/education/glossary/utxo-set
If you are an AI agent, LLM, or automated tool, a clean Markdown version of this page is available at: https://help.blockstream.com/education/glossary/utxo-set.md
Read
30 sources
- https://bitcoin.org/bitcoin.pdf
White paper sections 2, 4, 5, 6, 8, 9 and 10 (coins as signature chains, change, fees, confirmations, privacy)
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/consensus/consensus.h
COINBASE_MATURITY
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/primitives/transaction.h
COutPoint, CTxIn, CTxOut, scriptWitness
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/coins.h
Coin, CCoinsView, CCoinsViewCache
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/txdb.h
CCoinsViewDB and the chainstate directory
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/consensus/tx_verify.cpp
CheckTxInputs (missing or spent inputs, maturity, value in below out)
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/validation.cpp
BIP 30 enforcement, IsBIP30Repeat, IsBIP30Unspendable, BIP34_IMPLIES_BIP30_LIMIT
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/kernel/chainparams.cpp
BIP34Height and hash, m_assumeutxo_data heights and block hashes
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/policy/policy.h
DUST_RELAY_TX_FEE
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/policy/policy.cpp
GetDustThreshold comment with 546 and 294 sat thresholds
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/wallet/coincontrol.h
Coin control, avoid partial spends, avoid address reuse
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/wallet/rpc/coins.cpp
listunspent and getbalance help text
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/doc/design/assumeutxo.md
Background validation and the compiled snapshot hash check
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/doc/release-notes/release-notes-28.0.md
Assumeutxo mainnet parameters at height 840,000
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0030.mediawiki
BIP 30 specification and status
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0034.mediawiki
BIP 34 specification, motivation and status
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0141.mediawiki
Witness structure and txid definition
- https://bitcoinops.org/en/topics/assumeutxo/
Assumeutxo definition
- https://bitcoinops.org/en/topics/utreexo/
Utreexo definition
- https://bitcoinops.org/en/topics/coin-selection/
Coin selection definition
- https://bitcoinops.org/en/topics/output-linking/
Address reuse and dust attacks
- https://bitcoinops.org/en/topics/consensus-cleanup-soft-fork/
Early coinbase duplication and the proposed uniqueness rule
- https://bitcoinops.org/en/newsletters/2025/08/08/
Utreexo draft BIPs news item
- https://eprint.iacr.org/2017/1095
UTXO set analysis abstract (every node stores every output, dust)
- https://eprint.iacr.org/2019/611
Utreexo paper abstract (logarithmic accumulator, proof overhead)
- https://learnmeabitcoin.com/technical/transaction/utxo/
UTXO definition, address balance, chainstate database
- https://github.com/bitcoin/bitcoin/pull/28553
dumptxoutset coin count at block 840,000 in a review
- https://github.com/bitcoin/bitcoin/pull/31969
dumptxoutset coin count at block 880,000 in a review
- https://github.com/bitcoin/bips/pull/1923
Utreexo BIPs 181 to 183, draft status
- https://help.blockstream.com/education/glossary/utxo-set
Looked for a dated UTXO set size; not cited (see injections)