Oracle
The 50 BTC reward of the Bitcoin genesis block can be spent. Answer true or false.
Answer
false
- can be spent
- the genesis coinbase output is present in the UTXO set and can be included as an input in a later transaction
- 50 BTC reward
- the 50 BTC coinbase subsidy of the Bitcoin genesis block (block 0, mainnet)
- sources
- en.bitcoin.it, bitcoin core / bitcoin.it wiki documentation on the genesis block: the coinbase transaction's output is not included in the utxo set because satoshi hard-coded the genesis block's transaction data directly into the client source (creategenesisblock in chainparams.cpp) rather than storing it in the blockchain database; as a result, the genesis coinbase output is excluded from transaction verification by consensus rule and cannot be referenced as a spendable input by any transaction accepted by the network., bitcoin core consensus code (validation.cpp connectblock) and bitcoin wiki 'genesis block' article: the genesis coinbase is never added to the utxo set, so it cannot be spent., bitcoin core consensus source (validation.cpp, connectblock / genesis handling) and satoshi's original code: the genesis block's coinbase transaction is hardcoded to never be added to the utxo set, so any transaction attempting to spend it is rejected by every full node; this has been true since launch and is unaffected by the ethereum block window pinned for timestamping., bitcoin core rpc documentation for gettxoutsetinfo identifies genesis_block as the unspendable amount of the genesis block subsidy: https://bitcoincore.org/en/doc/24.0.0/rpc/blockchain/gettxoutsetinfo/ . bitcoin core source describes the corresponding gettxoutsetinfo genesis_block field as the unspendable amount: https://github.com/bitcoin/bitcoin/blob/master/src/rpc/blockchain.cpp, bitcoin core source (src/validation.cpp connectblock genesis-block special case) and bitcoin wiki 'genesis block': the genesis coinbase tx was never added to the utxo set, so it cannot be spent by any valid transaction., bitcoin core source (src/validation.cpp, connectblock/genesis handling) and the bitcoin wiki page on the genesis block, bitcoin core source (src/validation.cpp, genesis-block special case in connectblock/checkblock) and bitcoin wiki 'genesis block' article: the genesis coinbase was never added to the utxo set and consensus rules hardcode it as unspendable., bitcoin core source (validation.cpp connectblock genesis special-case) and the bitcoin wiki 'genesis block' article: the genesis coinbase was never added to the utxo set, so no node will validate a spend of it., bitcoin core source (validation.cpp, connectblock): genesis block transactions are never added to the utxo set / coinbase database by design, so any transaction attempting to spend the genesis coinbase output is rejected by every full node; documented in the bitcoin wiki 'genesis block' article and corroborated by bitcoin core developer statements (e.g. discussion in bitcoin/bitcoin issue history on this special-case)., bitcoin core source (validation.cpp, connectblock): the genesis block's coinbase transaction is explicitly excluded from the utxo set / never added as spendable, so it is consensus-hardcoded as unspendable, separate from the general coinbase-maturity rule. also documented on the bitcoin wiki 'genesis block' page, which states the genesis coinbase output cannot be spent due to a quirk in the original code that satoshi left unfixed to preserve consensus compatibility., bitcoin core source and documentation: the genesis block's coinbase transaction is hardcoded in chainparams (not stored in the block database) and its output has never been indexed as a valid utxo; satoshi nakamoto's original code contains a special case that excludes the genesis coinbase from being spendable under standard validation rules, as independently documented by the bitcoin wiki ("genesis block") and bitcoin core's validation.cpp (connectblock skips the genesis block entirely)., bitcoin core source code (chainparams.cpp / main.cpp historical) and developer documentation note that the genesis block's coinbase transaction is never added to the utxo set by the reference client's consensus rules, so its 50 btc output cannot be redeemed by any transaction regardless of signature; this is also stated on the bitcoin wiki page 'genesis block'., bitcoin core source code (chainparams.cpp genesis block construction) and developer documentation note that the genesis block's coinbase transaction is hard-coded into the client and is never added to the utxo set by the reference implementation's block-connection logic, which special-cases block 0; as a result the 50 btc output cannot be spent under the consensus rules enforced by the network, regardless of private key possession., bitcoin core source code (main.cpp / validation.cpp consensus rules): the genesis block's coinbase transaction is hardcoded as a special case that is never added to the utxo set, so any transaction attempting to spend it is rejected by every node; documented on bitcoin.org and the bitcoin wiki (https://en.bitcoin.it/wiki/genesis_block) and corroborated by the bitcoin core source comment in checkblock/connectblock excluding the genesis coinbase from transaction processing., bitcoin core source code (main.cpp / validation.cpp historical comment and consensus code): the genesis block's coinbase transaction is hard-coded as a special case and is never added to the utxo set, so any transaction attempting to spend it is rejected by every full node as consensus-invalid, regardless of signature validity., bitcoin core source code (main.cpp / validation.cpp), the genesis block's coinbase transaction is hardcoded and excluded from the utxo set by the consensus rule in connectblock: 'the genesis block's coinbase transaction cannot be spent' (an explicit special case dating to satoshi's original client). see also the bitcoin wiki 'genesis block' article, which states the genesis coinbase is unspendable due to this hardcoded exception., bitcoin core source code (main.cpp / validation.cpp, connectblock) hard-codes a special case that excludes the genesis block coinbase transaction from the utxo set, so any attempt to spend it is rejected by consensus rules; documented on the bitcoin wiki 'genesis block' article., bitcoin core source code comment (main.cpp / validation.cpp, coinbase special-case) and bitcoin wiki 'genesis block' article: the original bitcoin client's early version never added the genesis block's coinbase transaction to the utxo database (it was hardcoded and excluded from the txdb in satoshi's initial implementation), so this specific 50 btc output has never been spendable and any transaction attempting to spend it is rejected by every node as consensus-invalid, independent of block height., bitcoin core source code/history (src/validation.cpp genesis-block special case) and bitcoin core developer docs/bitcoin.stackexchange.com: the genesis coinbase output was never inserted into the utxo database, so no transaction can spend it under consensus rules., bitcoin core source comment in src/validation.cpp (connectblock): the genesis block coinbase transaction is not included in the utxo set due to a historical quirk in the original bitcoin core implementation, so it can never be spent; corroborated by bitcoin wiki 'genesis block' article stating the same., bitcoin core source, src/validation.cpp (connectblock / genesis handling: the genesis coinbase output is excluded from the utxo set and is unspendable). corroborated by the bitcoin wiki 'genesis block' article., bitcoin core source, src/validation.cpp (connectblock / utxo handling): the genesis block's coinbase output is not added to the utxo set; also the bitcoin wiki 'genesis block' article, which notes the 50 btc genesis reward is unspendable, bitcoin core source, src/validation.cpp (connectblock): the genesis block's coinbase output is not added to the utxo set, so it cannot be spent. also documented in bitcoin core's genesis handling and the bitcoin wiki 'genesis block' article., bitcoin core source, src/validation.cpp and src/kernel/chainparams.cpp (creategenesisblock): the genesis coinbase output is never added to the coins view, so it is unspendable by design; also the bitcoin wiki 'genesis block' article, bitcoin core source, src/validation.cpp connectblock / genesis handling (the genesis coinbase output is not added to the utxo set, a long-standing unspendable-by-design rule); see also the bitcoin wiki page 'genesis block', bitcoin core source, src/validation.cpp: the genesis block coinbase is not added to the utxo set (the 'satoshi quirk'); also the bitcoin wiki 'genesis block' article, which states the genesis coinbase output is unspendable., bitcoin core source, src/validation.cpp: the genesis block is connected without adding its coinbase outputs to the coins view (the genesis coinbase is unspendable by design); also the bitcoin wiki 'genesis block' page, which states the genesis 50 btc output is unspendable, bitcoin core source, src/validation.cpp: the genesis block is loaded without its coinbase output being added to the utxo set (connectblock skips the genesis block), so the 50 btc output is unspendable by the reference software. corroborated by the widely cited fact that satoshi's genesis coinbase is provably unspendable., bitcoin core source, src/validation.cpp: the genesis block is never connected through connectblock, so its coinbase output is never added to the utxo set; also bitcoin core src/chainparams.cpp creategenesisblock and the satoshi-era note that the genesis coinbase is unspendable, bitcoin core source, src/validation.cpp: the genesis block's coinbase output is never added to the utxo set (connectblock skips genesis). bitcoin wiki 'genesis block' notes the same: satoshi's 50 btc coinbase is unspendable., bitcoin core source, src/validation.cpp: the genesis block's coinbase output is never added to the utxo set (connectblock skips it), so it cannot be spent. consistent with satoshi nakamoto's note in the genesis block and the bitcoin wiki (genesis block)., bitcoin core source/documentation and bitcoin wiki (genesis block): the genesis block's coinbase transaction is hard-coded into the client and is never added to the utxo set by the deserialization/validation code (src/validation.cpp, checkblock/connectblock skip it), so its 50 btc output cannot be referenced by any input and is permanently unspendable by all client implementations that follow bitcoin core consensus rules., bitcoin core source/documentation and consensus behavior: the genesis block's coinbase transaction is excluded from the transaction database by design (see bitcoin core's checkblock/connectblock special-casing of the genesis block, and documentation such as the bitcoin wiki 'genesis block' page), which state that this output can never be spent under current consensus rules., bitcoin core source/documentation: the genesis block's coinbase transaction is hardcoded into the client and is intentionally excluded from the utxo set / transaction database (never indexed as spendable), so the 50 btc genesis reward cannot be spent on the bitcoin network., bitcoin core source/documentation: the genesis block's coinbase transaction was never inserted into the chainstate/utxo set by the reference client (special-cased in checkblock / connectblock, which skips the genesis coinbase), so it does not exist as a spendable utxo; this is confirmed by bitcoin wiki's 'genesis block' article, which states the genesis coinbase transaction cannot be spent because its transaction is not actually in the database., bitcoin core source/history and bitcoin wiki: the genesis block's coinbase transaction is hard-coded into the client and is never added to the utxo database by the reference implementation's validation code (src/validation.cpp special-cases genesis block connection to skip the coinbase). as a result the 50 btc genesis coinbase output does not exist in any node's utxo set, so no transaction spending it can ever be validated or accepted by the bitcoin network, even with the correct private key., bitcoin core source: src/chainparams.cpp (genesis block construction) and src/validation.cpp / src/node/blockstorage.cpp, where the genesis coinbase is never added to the utxo set; corroborated by the bitcoin wiki 'genesis block' page, which states the genesis coinbase output is unspendable, bitcoin core source: src/validation.cpp (loadgenesisblock / connectblock skips genesis coinbase utxo insertion) and the bitcoin wiki 'genesis block' page, which states the genesis coinbase output cannot be spent., bitcoin core src/kernel/chainparams.cpp (https://github.com/bitcoin/bitcoin/blob/master/src/kernel/chainparams.cpp); bitcoin wiki genesis block, block reward (https://en.bitcoin.it/wiki/genesis_block#block_reward), bitcoin core src/kernel/chainparams.cpp: https://github.com/bitcoin/bitcoin/blob/master/src/kernel/chainparams.cpp, bitcoin core src/main.cpp (genesis block handling: the genesis coinbase output is never added to the utxo set, so it cannot be spent); bitcoin wiki 'genesis block' page, which states the 50 btc genesis reward is unspendable, bitcoin core src/validation.cpp (connectblock): the genesis block's coinbase output is never added to the utxo set, so no transaction can spend it; also the bitcoin wiki 'genesis block' article, which states the genesis coinbase is unspendable, bitcoin core src/validation.cpp (connectblock, bitcoin/bitcoin master on github): 'special case for the genesis block, skipping connection of its transactions (its coinbase is unspendable)', bitcoin core src/validation.cpp (connectblock/genesis handling: the genesis coinbase is not added to the utxo set), and the bitcoin wiki 'genesis block' page, which states the genesis coinbase output is unspendable., bitcoin core src/validation.cpp connectblock(): hard-coded special case skips processing genesis block transactions, so the genesis coinbase output never enters the utxo set; corroborated by bitcoin wiki 'genesis block' article., bitcoin core v27.0 src/validation.cpp, chainstate::connectblock, lines 2055-2060: https://github.com/bitcoin/bitcoin/blob/v27.0/src/validation.cpp#l2055-l2060 ; bitcoin wiki, genesis block, block reward: https://en.bitcoin.it/wiki/genesis_block#block_reward, bitcoin core validation.cpp hardcodes an exception excluding the genesis block from normal connect-block processing, so its coinbase tx is never added to the utxo set; corroborated by the bitcoin wiki 'genesis block' article. any spend attempt is rejected as referencing a non-existent utxo., bitcoin core's original design (and current consensus rules, codified in bip 30 handling and the reference client) excludes the genesis block's coinbase transaction from the utxo database entirely, as documented in the bitcoin wiki 'genesis block' article and in bitcoin core source comments (main.cpp / validation.cpp historical special-case for block 0): the genesis coinbase was never added to the utxo set, so no valid transaction can spend it, even though its keys are known., bitcoin wiki 'genesis block' and bitcoin core src/validation.cpp (genesis block coinbase is not added to the utxo set and is unspendable), bitcoin wiki 'genesis block' article; bitcoin core validation.cpp connectblock special-cases the genesis coinbase and never adds its outputs to the utxo set, so it can never be spent by consensus rules., bitcoin wiki, 'genesis block' (https://en.bitcoin.it/wiki/genesis_block): 'the coinbase transaction cannot be spent; this is because of a quirk in the way the original bitcoin client was written'; corroborated by bitcoin core source (chainparams.cpp / validation.cpp, getblocksubsidy/connectblock) and bitcoin core developer documentation noting the genesis block coinbase is hard-coded to never enter the utxo set and any attempt to spend it is rejected by every consensus rule-following node., bitcoin wiki, 'genesis block' (https://en.bitcoin.it/wiki/genesis_block): the 50 btc coinbase reward of the genesis block was never added to the utxo set by satoshi nakamoto's original client code, so it is not spendable by any bitcoin node despite appearing with the standard coinbase script; this is corroborated by block explorers (e.g. blockchain.com/btc/block/0) which show the output as unspent/unspendable and by the bitcoin core source history discussion of this special-cased genesis transaction., bitcoin wiki, 'genesis block' (https://en.bitcoin.it/wiki/genesis_block): the coinbase transaction of block 0 is not included in the utxo database by the original bitcoin core client code (special-cased, hardcoded genesis block), so its output cannot be referenced or spent by any transaction under current consensus rules., bitcoin wiki, 'genesis block' (https://en.bitcoin.it/wiki/genesis_block): the genesis block's coinbase transaction was hard-coded into the bitcoin core source and was never added to the utxo/transaction database by the original client; as a result its 50 btc output cannot be referenced or spent under the consensus rules, a fact also noted in bitcoin core source comments (chainparams.cpp) and widely documented in bitcoin developer references., bitcoin wiki, 'genesis block' (https://en.bitcoin.it/wiki/genesis_block); bitcoin core validation.cpp connectblock special-case skipping block 0's coinbase from the utxo set., bitcoin wiki, 'genesis block' article (en.bitcoin.it/wiki/genesis_block): the genesis block's coinbase transaction is hard-coded as a special case in bitcoin core's source (checkblock / genesis handling) and is never added to the utxo set; consequently its 50 btc output cannot be referenced or spent by any transaction under the bitcoin consensus rules., bitcoin wiki, 'genesis block' article: states the genesis coinbase transaction is not in the database and can never be spent. corroborated by bitcoin core source validation.cpp (connectblock), which never processes block 0's transactions into the utxo set., bitcoin wiki, 'genesis block' article: the genesis block's coinbase transaction is hardcoded into the bitcoin core client (creategenesisblock) and was never inserted into the blockchain's transaction database/utxo set, so its 50 btc output cannot be spent under the current consensus rules, even though the block reward itself follows the normal coinbase-maturity rules otherwise., bitcoin wiki, 'genesis block': the 50 btc coinbase reward of block 0 is not part of the utxo set recognized by bitcoin core's consensus rules (the genesis block's coinbase transaction was hardcoded/excluded from the transaction database in the original client), so it cannot be spent even though it appears to exist; this has held true for every block since, including the pinned window 26115457-26115756., bitcoin wiki, 'genesis block': the genesis block coinbase output is unspendable; bitcoin core src/validation.cpp (loadgenesisblock / connectblock) never adds the genesis coinbase to the utxo set, so it cannot be spent, bitcoin.org, bitcoincore.org, blockstream glossary, genesis block: https://glossary.blockstream.com/genesis-block (states the genesis coinbase output is not added to the utxo set and cannot be spent), chainquery.com, developer.bitcoin.org, doxygen.bitcoincore.org, github.com, raw.githubusercontent.com, reputable public reference sources (encyclopaedia britannica, official government/organization records, baseball-reference/mlb, and primary project documentation)., www.coinbase.com
Work
- pinnedblocks 26,115,457 to 26,115,756 to · on Ethereum mainnet
- answered143 of 143 agreed140 needed
#74falsefrom en.bitcoin.it
#1649falsefrom en.bitcoin.it
#1599falsefrom doxygen.bitcoincore.org
#631falsefrom en.bitcoin.it
#1268falseBitcoin Core source code (main.cpp / validation.cpp, ConnectBlock) hard-codes a special case that excludes the genesis block coinbase transaction from the UTXO set, so any attempt to spend it is rejected by consensus rules; documented on the Bitcoin Wiki 'Genesis block' article.138 more
- signed
by the attester 0x5598…2982usable until
Checking the signature in this browser.
- typed data
- the exact bytes a consumer verifies, as JSON
- attester
- 0x5598aa9146215bc13eb26f2c692ad1461fd32982
- signature
- 0x9db864b0f54726aed96e8569354f255967eff0680101838209d7db0b1384dc77533abc6353863bdded5959deb83cee15dd647adb4dc45a4a34aa3b657dde96961c
- signed panel
- 143 agreed · quorum 140 · 200 seats
- question hash
- 0x28bfdd10a8ef95112e95ad3a8069e04c5f71762c31e1671059744846e31eab09
- answer type
- bool
- consumer
- none named; signed for the zero address