Blocklore
Esc

Type to search every published claim: statements, sources and topics.

Enter opens the claim; with no match, suggests the questionUp and down to move
976,842
Reading as Holder. What matters when you hold your own coins.16 of 37 claims
How deep to read

What it isCurious

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.1: open 1 source
DefinitionCuriousEstablishedMedium confidence
We define an electronic coin as a chain of digital signatures. Each owner transfers the coin to the next by digitally signing a hash of the previous transaction and the public key of the next owner
Section 2, Transactions, read 2026-11-20
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 1/1History, hash and citation
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.2: open 2 sources
How it worksCuriousEstablishedMedium confidence
T2learnmeabitcoin, UTXODocumentation, says this directly
UTXOs that get spent in a transaction are removed from the database, and the new outputs are added to the database.
UTXO set section, read 2026-11-20
To allow value to be split and combined, transactions contain multiple inputs and outputs.
Section 9, Combining and Splitting Value, read 2026-11-20
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 2/2History, hash and citation
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.3: open 1 source
How it worksCuriousEstablishedMedium confidence
Normally there will be either a single input from a larger previous transaction or multiple inputs combining smaller amounts, and at most two outputs: one for the payment, and one returning the change, if any, back to the sender.
Section 9, Combining and Splitting Value, read 2026-11-20
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 1/1History, hash and citation

In your walletUser

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.4: open 2 sources
FactUserEstablishedMedium confidence
T2learnmeabitcoin, UTXODocumentation, says this directly
Therefore, the balance of an address is just the sum of all the UTXOs that have been locked to that address.
Address balance, read 2026-11-20
Returns array of unspent transaction outputs
listunspent RPC description, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/wallet/rpc/coins.cpp, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/wallet/rpc/coins.cpp | grep -nF 'Returns array of unspent transaction outputs'
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 2/2, code 1/1History, hash and citation
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.5: open 2 sources
How it worksUserEstablishedMedium confidence
Normally there will be either a single input from a larger previous transaction or multiple inputs combining smaller amounts
Section 9, Combining and Splitting Value, read 2026-11-20
T2Bitcoin Optech topic, Coin selectionBitcoin Optech, supports part of it
Coin selection is the method a wallet uses to choose which of its UTXOs to spend in a particular transaction.
Topic summary, read 2026-11-20
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 2/2History, hash and citation
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.6: open 2 sources
How it worksUserEstablishedHigh confidence
If the output value of a transaction is less than its input value, the difference is a transaction fee
Section 6, Incentive, read 2026-11-20
return state.Invalid(TxValidationResult::TX_CONSENSUS, "bad-txns-in-belowout",
Consensus::CheckTxInputs, value-in below value-out, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/consensus/tx_verify.cpp, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/consensus/tx_verify.cpp | grep -nF 'bad-txns-in-belowout'
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 2/2, code 1/1History, hash and citation
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.7: open 2 sources
How it worksUserEstablishedHigh confidence
Nodes accept the block only if all transactions in it are valid and not already spent.
Section 5, Network, step 5, read 2026-11-20
return state.Invalid(TxValidationResult::TX_MISSING_INPUTS, "bad-txns-inputs-missingorspent",
Consensus::CheckTxInputs, missing or spent inputs, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/consensus/tx_verify.cpp, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/consensus/tx_verify.cpp | grep -nF 'bad-txns-inputs-missingorspent'
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 2/2, code 1/1History, hash and citation
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.8: open 2 sources
How it worksUserEstablishedMedium confidence
and blocks added after it further confirm the network has accepted it.
Section 8, Simplified Payment Verification, read 2026-11-20
As later blocks are chained after it, the work to change the block would include redoing all the blocks after it.
Section 4, Proof-of-Work, read 2026-11-20
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 2/2History, hash and citation

Privacy and coin controlHolder

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.9: open 1 source
FactHolderEstablishedMedium confidence
Some linking is still unavoidable with multi-input transactions, which necessarily reveal that their inputs were owned by the same owner.
Section 10, Privacy, read 2026-11-20
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 1/1History, hash and citation
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.10: open 2 sources
FactHolderEstablishedMedium confidence
As an additional firewall, a new key pair should be used for each transaction to keep them from being linked to a common owner.
Section 10, Privacy, read 2026-11-20
T2Bitcoin Optech topic, Output linkingBitcoin Optech, supports part of it
Methods for limiting the loss of privacy from output linking fall under the category of reuse avoidance.
Topic summary, read 2026-11-20
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 2/2History, hash and citation
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.11: open 2 sources
DefinitionHolderEstablishedMedium confidence
T2Bitcoin Optech topic, Output linkingBitcoin Optech, says this directly
Output linking, also called address reuse, occurs when a user receives two or more payments to the same public key or other unique script element.
Topic summary, read 2026-11-20
T2Bitcoin Optech topic, Output linkingBitcoin Optech, says this directly
other users can reasonably assume that the same person received all of those payments even if the payments are later spent in separate transactions.
Topic summary, second paragraph, read 2026-11-20
Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2History, hash and citation
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.12: open 1 source
How it worksHolderEstablishedMedium confidence
T2Bitcoin Optech topic, Output linkingBitcoin Optech, says this directly
This may happen because the user reuses an address out of ignorance or as the result of deliberate targeting, as in a dust attack.
Topic summary, read 2026-11-20
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 1/1History, hash and citation
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.13: open 2 sources
FactHolderEstablishedHigh confidence
The output will be included in the transaction even if it's not the most optimal choice.
CCoinControl, doc comment of Select, read 2026-11-20
T2Bitcoin Optech topic, Coin selectionBitcoin Optech, background
Coin selection is the method a wallet uses to choose which of its UTXOs to spend in a particular transaction.
Topic summary, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/wallet/coincontrol.h, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/wallet/coincontrol.h | grep -nF 'The output will be included in the transaction even if it'"'"'s not the most optimal choice.'
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 2/2, code 1/1History, hash and citation
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.14: open 2 sources
FactHolderEstablishedHigh confidence
Avoid partial use of funds sent to a given address
CCoinControl, m_avoid_partial_spends and m_avoid_address_reuse, read 2026-11-20
Forbids inclusion of dirty (previously used) addresses
CCoinControl, m_avoid_address_reuse, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/wallet/coincontrol.h, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/wallet/coincontrol.h | grep -nF 'bool m_avoid_partial_spends = DEFAULT_AVOIDPARTIALSPENDS;'
bitcoin/bitcoin at f498a5a671 contains this text in src/wallet/coincontrol.h, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/wallet/coincontrol.h | grep -nF 'bool m_avoid_address_reuse = false;'
Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, code 2/2History, hash and citation
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.15: open 3 sources
FactHolderEstablishedHigh confidence
If you'd pay more in fees than the value of the output
GetDustThreshold, opening comment, read 2026-11-20
546 satoshis at the default rate of 3000 sat/kvB.
GetDustThreshold, opening comment, non-segwit example, read 2026-11-20
294 satoshis at the default rate of 3000 sat/kvB.
GetDustThreshold, opening comment, P2WPKH example, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/policy/policy.h, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/policy/policy.h | grep -nF 'inline constexpr unsigned int DUST_RELAY_TX_FEE{3000};'
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 3/3, code 1/1History, hash and citation

In the codeBuilder

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.16: open 2 sources
DefinitionBuilderEstablishedHigh confidence
An outpoint - a combination of a transaction hash and an index n into its vout
doc comment above class COutPoint, read 2026-11-20
T1Bitcoin Core src/primitives/transaction.h, CTxInSource code, supports part of it
An input of a transaction. It contains the location of the previous
doc comment above class CTxIn, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/primitives/transaction.h, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/primitives/transaction.h | grep -nF 'uint32_t n;'
bitcoin/bitcoin at f498a5a671 contains this text in src/primitives/transaction.h, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/primitives/transaction.h | grep -nF 'COutPoint prevout;'
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 2/2, code 2/2History, hash and citation
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.17: open 2 sources
DefinitionBuilderEstablishedHigh confidence
T1Bitcoin Core src/primitives/transaction.h, CTxOutSource code, says this directly
CScript scriptPubKey;
class CTxOut, members nValue and scriptPubKey, read 2026-11-20
T1Bitcoin Core src/primitives/transaction.h, CTxOutSource code, supports part of it
An output of a transaction. It contains the public key that the next input
doc comment above class CTxOut, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/primitives/transaction.h, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/primitives/transaction.h | grep -nF 'CAmount nValue;'
bitcoin/bitcoin at f498a5a671 contains this text in src/primitives/transaction.h, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/primitives/transaction.h | grep -nF 'CScript scriptPubKey;'
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 2/2, code 2/2History, hash and citation
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.18: open 3 sources
How it worksBuilderEstablishedHigh confidence
A new data structure, <code>witness</code>, is defined. Each transaction will have 2 IDs.
Specification, Transaction ID, read 2026-11-20
Definition of <code>txid</code> remains unchanged: the double SHA256 of the traditional serialization format:
Specification, Transaction ID, read 2026-11-20
T1Bitcoin Core src/primitives/transaction.h, CTxInSource code, says this directly
CScriptWitness scriptWitness;
class CTxIn, members, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/primitives/transaction.h, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/primitives/transaction.h | grep -nF 'CScriptWitness scriptWitness;'
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 3/3, code 1/1History, hash and citation
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.19: open 2 sources
FactBuilderEstablishedHigh confidence
Coinbase transaction outputs can only be spent after this number of new blocks (network rule)
COINBASE_MATURITY and its comment, read 2026-11-20
if (coin.IsCoinBase() && nSpendHeight - coin.nHeight < COINBASE_MATURITY) {
Consensus::CheckTxInputs, coinbase maturity check, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/consensus/consensus.h, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/consensus/consensus.h | grep -nF 'inline constexpr int COINBASE_MATURITY = 100;'
bitcoin/bitcoin at f498a5a671 contains this text in src/consensus/tx_verify.cpp, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/consensus/tx_verify.cpp | grep -nF 'bad-txns-premature-spend-of-coinbase'
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 2/2, code 2/2History, hash and citation
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.20: open 3 sources
How it worksBuilderEstablishedHigh confidence
T1Bitcoin Core src/coins.h, class CoinSource code, says this directly
A UTXO entry.
doc comment above class Coin, read 2026-11-20
T1Bitcoin Core src/coins.h, class CoinSource code, says this directly
uint32_t nHeight : 31;
class Coin, fCoinBase and nHeight members, read 2026-11-20
if (coin.IsCoinBase() && nSpendHeight - coin.nHeight < COINBASE_MATURITY) {
Consensus::CheckTxInputs, coinbase maturity check, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/coins.h, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/coins.h | grep -nF 'bool fCoinBase : 1;'
bitcoin/bitcoin at f498a5a671 contains this text in src/coins.h, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/coins.h | grep -nF 'uint32_t nHeight : 31;'
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 3/3, code 2/2History, hash and citation
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.21: open 3 sources
TraceBuilderEstablishedHigh confidence
T1Bitcoin Core src/coins.h, CCoinsViewSource code, says this directly
Pure abstract view on the open txout dataset.
doc comment above class CCoinsView, read 2026-11-20
T1Bitcoin Core src/coins.h, CCoinsViewCacheSource code, says this directly
CCoinsView that adds a memory cache for transactions to another CCoinsView
doc comment above class CCoinsViewCache, read 2026-11-20
T1Bitcoin Core src/txdb.h, CCoinsViewDBSource code, says this directly
CCoinsView backed by the coin database (chainstate/)
doc comment above class CCoinsViewDB, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/coins.h, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/coins.h | grep -nF 'class CCoinsViewCache : public CCoinsViewBacked'
bitcoin/bitcoin at f498a5a671 contains this text in src/txdb.h, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/txdb.h | grep -nF 'class CCoinsViewDB final : public CCoinsView'
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 3/3, code 2/2History, hash and citation
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.22: open 3 sources
How it worksBuilderEstablishedMedium confidence
T2learnmeabitcoin, UTXODocumentation, says this directly
In Bitcoin Core, all of the UTXOs are stored in the chainstate database:
UTXO set section, read 2026-11-20
T1Bitcoin Core src/txdb.h, CCoinsViewDBSource code, supports part of it
CCoinsView backed by the coin database (chainstate/)
doc comment above class CCoinsViewDB, read 2026-11-20
Bitcoin relies on the Unspent Transaction Outputs (UTXO) set to efficiently verify new generated transactions.
Abstract, read 2026-11-20
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 3/3History, hash and citation

Duplicate transactionsBuilder

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.23: open 2 sources
FactBuilderEstablishedHigh confidence
T1BIP 30, Duplicate transactionsBIP, says this directly
Blocks are not allowed to contain a transaction whose identifier matches that of an earlier, not-fully-spent transaction in the same chain.
Specification, read 2026-11-20
T1Bitcoin Core src/validation.cpp, ConnectBlockSource code, says this directly
Do not allow blocks that contain transactions which 'overwrite' older transactions,
Chainstate::ConnectBlock, BIP30 check, read 2026-11-20
BIP 30's Status is "Deployed" on the default branch.
Run it yourselfcurl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0030.mediawiki | grep -m1 -E '^ *Statuss?:'
bitcoin/bitcoin at f498a5a671 contains this text in src/validation.cpp, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/validation.cpp | grep -nF 'bad-txns-BIP30'
Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, code 2/2History, hash and citation
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.24: open 3 sources
FactBuilderEstablishedHigh confidence
T1BIP 34, Block v2, Height in CoinbaseBIP, says this directly
Add height as the first item in the coinbase transaction's scriptSig, and increase block version to 2.
Specification, read 2026-11-20
T1BIP 34, Block v2, Height in CoinbaseBIP, says this directly
Enforce block and transaction uniqueness, and assist unconnected block validation.
Motivation, read 2026-11-20
consensus.BIP34Height = 227931;
CMainParams, BIP34Height and BIP34Hash, read 2026-11-20
BIP 34's Status is "Deployed" on the default branch.
Run it yourselfcurl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0034.mediawiki | grep -m1 -E '^ *Statuss?:'
bitcoin/bitcoin at f498a5a671 contains this text in src/kernel/chainparams.cpp, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/kernel/chainparams.cpp | grep -nF 'consensus.BIP34Height = 227931;'
Block 227,931 has hash 000000000000024b...
Run it yourselfbitcoin-cli getblockhash 227931
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 3/3, code 2/2, chain 1/1 (esplora pair agreed)History, hash and citation
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.25: open 2 sources
TraceResearcherEstablishedHigh confidence
T1Bitcoin Core src/validation.cpp, IsBIP30RepeatSource code, says this directly
return (block_index.nHeight==91842 && block_index.GetBlockHash() == uint256{
IsBIP30Repeat, read 2026-11-20
T1Bitcoin Core src/validation.cpp, ConnectBlockSource code, says this directly
bool fEnforceBIP30 = !IsBIP30Repeat(*pindex);
Chainstate::ConnectBlock, fEnforceBIP30, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/validation.cpp, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/validation.cpp | grep -nF 'block_index.nHeight==91880'
Block 91,842 has hash 00000000000a4d0a...
Run it yourselfbitcoin-cli getblockhash 91842
Block 91,880 has hash 00000000000743f1...
Run it yourselfbitcoin-cli getblockhash 91880
Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, code 1/1, chain 2/2 (esplora pair agreed)History, hash and citation
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.26: open 1 source
TraceResearcherEstablishedMedium confidence
return (block_height==91722 && block_hash == uint256{
IsBIP30Unspendable, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/validation.cpp, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/validation.cpp | grep -nF 'block_height==91812'
Block 91,722 has hash 00000000000271a2...
Run it yourselfbitcoin-cli getblockhash 91722
Block 91,812 has hash 00000000000af0ae...
Run it yourselfbitcoin-cli getblockhash 91812
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 1/1, code 1/1, chain 2/2 (esplora pair agreed)History, hash and citation
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.27: open 3 sources
How it worksResearcherEstablishedHigh confidence
T1Bitcoin Core src/validation.cpp, ConnectBlockSource code, says this directly
if (fEnforceBIP30 || pindex->nHeight >= BIP34_IMPLIES_BIP30_LIMIT) {
Chainstate::ConnectBlock, BIP30 enforcement condition, read 2026-11-20
greater than 1,983,702, so we simply remove the optimization to skip
Chainstate::ConnectBlock, comment above BIP34_IMPLIES_BIP30_LIMIT, read 2026-11-20
T2Bitcoin Optech topic, Consensus cleanup soft forkBitcoin Optech, says this directly
Some early coinbase transactions exhibit patterns that would allow them to be replayed in future blocks.
Duplicate transaction vector, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/validation.cpp, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/validation.cpp | grep -nF 'static constexpr int BIP34_IMPLIES_BIP30_LIMIT = 1983702;'
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 3/3, code 1/1History, hash and citation
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.Speculative28: open 1 source
FactResearcherSpeculativeMedium confidence
T2Bitcoin Optech topic, Consensus cleanup soft forkBitcoin Optech, says this directly
enforces that future coinbase transactions are unique without needing to enforce BIP30 checks for those blocks.
Duplicate transaction vector, read 2026-11-20
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 1/1History, hash and citation

Size of the UTXO setResearcher

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.29: open 2 sources
FactResearcherEstablishedMedium confidence
no matter its type, age, value or length is stored in every full node.
Abstract, read 2026-11-20
analysis of the volume of dust and unprofitable outputs included in the set,
Abstract, read 2026-11-20
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 2/2History, hash and citation
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.30: open 2 sources
FactResearcherEstablishedMedium confidence
T1Bitcoin Core PRPull request, says this directly
"coins_written": 176948713,
Approving review, dumptxoutset output for height 840,000, read 2026-11-20
T1Bitcoin Core PRPull request, says this directly
"coins_written": 184821030,
Approving review, dumptxoutset output for height 880,000, read 2026-11-20
Block 840,000 has hash 0000000000000000...
Run it yourselfbitcoin-cli getblockhash 840000
Block 880,000 has hash 0000000000000000...
Run it yourselfbitcoin-cli getblockhash 880000
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 2/2, chain 2/2 (esplora pair agreed)History, hash and citation
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.31: open 3 sources
DefinitionResearcherEstablishedHigh confidence
T2Bitcoin Optech topic, AssumeUTXOBitcoin Optech, says this directly
is a proposed mode for bootstrapping new full nodes that allows them to postpone verifying old block chain history
Topic summary, read 2026-11-20
T2Bitcoin Optech topic, AssumeUTXOBitcoin Optech, says this directly
the node would also download and verify older blocks in the background so that it could eventually prove
Topic summary, read 2026-11-20
T2Bitcoin Core doc/design/assumeutxo.mdDocumentation, says this directly
which is responsible for doing full validation of the assumed-valid parts of the chain.
Snapshot chainstate hits network tip, read 2026-11-20
Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 3/3History, hash and citation
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.32: open 2 sources
EventResearcherEstablishedHigh confidence
T1Bitcoin Core 28.0 release notesRelease notes, says this directly
AssumeUTXO mainnet parameters have been added for height 840,000.
Updated RPCs, read 2026-11-20
T1Bitcoin Core 28.0 release notesRelease notes, says this directly
This means the `loadtxoutset` RPC can now be used on mainnet with the matching UTXO set from that height.
Updated RPCs, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/kernel/chainparams.cpp, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/kernel/chainparams.cpp | grep -nF '.height = 840'"'"'000,'
Block 840,000 has hash 0000000000000000...
Run it yourselfbitcoin-cli getblockhash 840000
Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, code 1/1, chain 1/1 (esplora pair agreed)History, hash and citation
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.33: open 2 sources
FactResearcherEstablishedHigh confidence
.height = 965'000,
CMainParams, m_assumeutxo_data, last entry, read 2026-11-20
T2Bitcoin Core doc/design/assumeutxo.mdDocumentation, says this directly
ensure it matches the compiled value in `CMainParams::m_assumeutxo_data`.
Background chainstate hits snapshot base block, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/kernel/chainparams.cpp.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/kernel/chainparams.cpp | grep -nF '.height = 910'"'"'000,'
bitcoin/bitcoin at f498a5a671 contains this text in src/kernel/chainparams.cpp.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/kernel/chainparams.cpp | grep -nF '.height = 935'"'"'000,'
bitcoin/bitcoin at f498a5a671 contains this text in src/kernel/chainparams.cpp, and still does on the default branch.
Run it yourselfgit clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/kernel/chainparams.cpp | grep -nF '.height = 965'"'"'000,'
Block 880,000 has hash 0000000000000000...
Run it yourselfbitcoin-cli getblockhash 880000
Checked at block 976,783, 20 Nov 2026, 20:55 UTC: recheck, quotes 2/2, code 3/3, chain 1/1 (esplora pair agreed)History, hash and citation
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.34: open 3 sources
DefinitionResearcherEstablishedHigh confidence
We introduce a hash based accumulator to locally represent the UTXO set, which is logarithmic in the size of the full set.
Abstract, read 2026-11-20
Nodes attach and propagate inclusion proofs to the inputs of transactions
Abstract, read 2026-11-20
T2Bitcoin Optech topic, UtreexoBitcoin Optech, says this directly
Utreexo is a proposed alternative to the UTXO set for allowing full nodes to obtain and verify information
Topic summary, read 2026-11-20
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 3/3History, hash and citation
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.35: open 1 source
FactResearcherEstablishedMedium confidence
In our simulations of downloading Bitcoin's blockchain up to early 2019 with 500MB of RAM allocated for caching, the proofs only add approximately 25% to the amount otherwise downloaded.
Abstract, read 2026-11-20
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 1/1History, hash and citation
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.36: open 2 sources
FactResearcherEstablishedMedium confidence
These are the 3 BIPs that describe Utreexo, a consensus-compatible (non-soft fork) way to send and verify transactions
PR description, read 2026-11-20
The first BIP specifies the structure of the Utreexo accumulator, which allows a node to store
News, Draft BIPs proposed for Utreexo, read 2026-11-20
Checked at block 976,842, 21 Nov 2026, 04:28 UTC: recheck, quotes 2/2History, hash and citation