Segregated Witness (SegWit)
Reading as Holder. What matters when you hold your own coins.7 of 29 claims
Addresses and feesUser
SegWit's consensus rules have been enforced on the Bitcoin mainnet since block 481,824, mined on 24 August 2017, and Bitcoin Core records that height together with the block's hash in its mainnet parameters.1: open 2 sources
EventUserEstablishedHigh confidence
T1Bitcoin Core src/kernel/chainparams.cpp, CMainParamsSource code, says this directly
consensus.SegwitHeight = 481824; // 0000000000000000001c8018d9cb3b742ef25114f27563e3fc4a1902167f9893
CMainParams, consensus.SegwitHeight, read 2026-11-20
T1Block 481,824The chain, says this directly
Block header, timestamp 1503539857 (24 August 2017, 01:57:37 UTC), 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 yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/kernel/chainparams.cpp | grep -nF 'consensus.SegwitHeight = 481824; // 0000000000000000001c8018d9cb3b742ef25114f27563e3fc4a1902167f9893'Block 481,824 has hash 0000000000000000...
Run it yourself
bitcoin-cli getblockhash 481824Block 481,824's header has time = 1503539857.
Run it yourself
bitcoin-cli getblockheader $(bitcoin-cli getblockhash 481824) | grep '"time"'Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 2/2, code 1/1, chain 2/2 (esplora pair agreed)History, hash and citation
Native SegWit version 0 addresses on the Bitcoin mainnet use the Bech32 format defined in BIP 173 and start with "bc1q", for example the BIP's sample P2WPKH address bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4; BIP 173 requires encoders to output them in lowercase.2: open 3 sources
FactUserEstablishedHigh confidence
T1BIP 173, Base32 address format for native v0-16 witness outputsBIP, says this directly
bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4
Examples, Mainnet P2WPKH, read 2026-11-20
T1BIP 173, Base32 address format for native v0-16 witness outputsBIP, says this directly
Encoders MUST always output an all lowercase Bech32 string.
Specification, Bech32, encoding case, read 2026-11-20
T2Bitcoin Optech topic, Bech32(m)Bitcoin Optech, supports part of it
Bech32 and Bech32m are address formats used to pay native segwit outputs.
Topic description, 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 yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/kernel/chainparams.cpp | grep -nF 'bech32_hrp = "bc";'Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 3/3, code 1/1History, hash and citation
BIP 173 states that the Bech32 checksum used by native SegWit addresses guarantees detection of any error affecting at most 4 characters; BIP 350 later described a weakness with inserted or deleted characters, which it says does not affect version 0 addresses because they are restricted to two specific lengths.3: open 4 sources
How it worksUserEstablishedMedium confidence
T1BIP 173, Base32 address format for native v0-16 witness outputsBIP, says this directly
guarantees detection of any error affecting at most 4 characters
Specification, Bech32, checksum, read 2026-11-20
T1BIP 350, Bech32m format for v1+ witness addressesBIP, says this directly
whenever the final character is a 'p', inserting or deleting any number of 'q' characters immediately preceding it does not invalidate the checksum.
Motivation, read 2026-11-20
T1BIP 350, Bech32m format for v1+ witness addressesBIP, says this directly
This does not affect existing uses of witness version 0 BIP173 addresses due to their restriction to two specific lengths,
Motivation, read 2026-11-20
T2Bitcoin Optech topic, Bech32(m)Bitcoin Optech, supports part of it
includes an error-correction code that can catch almost all address typos
Topic description, read 2026-11-20
Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 4/4History, hash and citation
BIP 141 defines a transaction's virtual size, measured in vbytes, as its transaction weight divided by 4 and rounded up to the next integer.4: open 1 source
DefinitionUserEstablishedMedium confidence
T1BIP 141, Segregated Witness (Consensus layer)BIP, says this directly
/ 4 (rounded up to the next integer).
Specification, Transaction size calculations, read 2026-11-20
Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 1/1History, hash and citation
For a typical transaction with one input and two outputs, Bitcoin Optech calculated in April 2019 that spending a native SegWit (P2WPKH) output takes 141 vbytes against 220 vbytes for a legacy P2PKH output, about 35% less, so the same fee rate in sat/vB costs less in total.5: open 2 sources
FactUserEstablishedMedium confidence
T2Bitcoin Optech Newsletter, 16 April 2019Bitcoin Optech, says this directly
Spending P2WPKH output has a size of 141 vbytes (16% savings vs P2SH-P2WPKH or 35% vs P2PKH)
Bech32 sending support, published 2019-04-16, read 2026-11-20
T2Bitcoin Optech Newsletter, 16 April 2019Bitcoin Optech, says this directly
Spending P2PKH has a total transaction size of 220 vbytes
Bech32 sending support, published 2019-04-16, read 2026-11-20
Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 2/2History, hash and citation
Why wallets use itHolder
As of block 976,753, the default for Bitcoin Core's -addresstype wallet option is bech32 (native SegWit); the Bitcoin Core 0.20.0 release notes record the change that made the wallet use bech32 addresses by default when used through RPC and create native SegWit change outputs.6: open 2 sources
FactBuilderEstablishedHigh confidence
T1Bitcoin Core 0.20.0 release notes, WalletRelease notes, says this directly
The wallet now by default uses bech32 addresses when using RPC, and creates native segwit change outputs.
Notable changes, Wallet, read 2026-11-20
T1Bitcoin Core src/wallet/wallet.h, DEFAULT_ADDRESS_TYPESource code, says this directly
inline constexpr OutputType DEFAULT_ADDRESS_TYPE{OutputType::BECH32};
DEFAULT_ADDRESS_TYPE, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/wallet/wallet.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/wallet/wallet.h | grep -nF 'inline constexpr OutputType DEFAULT_ADDRESS_TYPE{OutputType::BECH32};'Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 2/2, code 1/1History, hash and citation
Under BIP 143, each signature on a SegWit version 0 input commits to the amount of the input it signs, which BIP 143 says lets an offline signing device learn that amount from an untrusted source; Bitcoin Optech reported in June 2020 that this proved insufficient against a fee overpayment attack on multi-input transactions.7: open 3 sources
How it worksHolderEstablishedMedium confidence
T1BIP 143, Transaction Signature Verification for Version 0 Witness ProgramBIP, says this directly
a cold wallet may safely sign a transaction by learning the value from an untrusted source.
Motivation, read 2026-11-20
T1BIP 143, Transaction Signature Verification for Version 0 Witness ProgramBIP, says this directly
and to cover the input value by the signature.
Abstract, read 2026-11-20
T2Bitcoin Optech Newsletter, 10 June 2020Bitcoin Optech, says this directly
Unfortunately, signing a single UTXO’s amount turned out to be insufficient.
News, Fee overpayment attack on multi-input segwit transactions, published 2020-06-10, read 2026-11-20
Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 3/3History, hash and citation
How it worksBuilder
Under BIP 141 every transaction has two identifiers: the txid, the double SHA-256 of the serialization without witness data (unchanged from before SegWit), and the wtxid, the double SHA-256 of the serialization that includes the witness.8: open 2 sources
DefinitionBuilderEstablishedMedium confidence
T1BIP 141, Segregated Witness (Consensus layer)BIP, says this directly
remains unchanged: the double SHA256 of the traditional serialization format:
Specification, Transaction ID, read 2026-11-20
T1BIP 141, Segregated Witness (Consensus layer)BIP, says this directly
is defined: the double SHA256 of the new serialization with witness data:
Specification, Transaction ID, read 2026-11-20
Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 2/2History, hash and citation
Since SegWit, a Bitcoin block's size limit is expressed in weight units: weight is the block's size without witness data times 3 plus its full size, and a valid block may weigh at most 4,000,000 weight units (BIP 141).9: open 3 sources
FactBuilderEstablishedHigh confidence
T1Bitcoin Core src/consensus/consensus.h, MAX_BLOCK_WEIGHTSource code, says this directly
The maximum allowed weight for a block, see BIP 141 (network rule)
MAX_BLOCK_WEIGHT, read 2026-11-20
T1Bitcoin Core src/consensus/validation.h, GetTransactionWeight and GetBlockWeightSource code, says this directly
weight = (stripped_size * 3) + total_size.
Comment above GetTransactionWeight, read 2026-11-20
T1BIP 141, Segregated Witness (Consensus layer)BIP, supports part of it
≤ 4,000,000.
Specification, Block size, 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 yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/consensus/consensus.h | grep -nF 'inline constexpr unsigned int MAX_BLOCK_WEIGHT{4'"'"'000'"'"'000};'BIP 141's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0141.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 3/3, code 2/2History, hash and citation
Under SegWit's weight formula, each byte of non-witness transaction data counts as 4 weight units and each byte of witness data counts as 1; Bitcoin Core names this factor of 4 WITNESS_SCALE_FACTOR.10: open 2 sources
How it worksBuilderEstablishedHigh confidence
T1Bitcoin Core src/consensus/validation.h, GetTransactionWeightSource code, says this directly
These implement the weight = (stripped_size * 4) + witness_size formula,
Comment above GetTransactionWeight, read 2026-11-20
T1Bitcoin Core src/consensus/consensus.h, WITNESS_SCALE_FACTORSource code, says this directly
inline constexpr int WITNESS_SCALE_FACTOR = 4;
WITNESS_SCALE_FACTOR, 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 yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/consensus/consensus.h | grep -nF 'inline constexpr int WITNESS_SCALE_FACTOR = 4;'bitcoin/bitcoin at f498a5a671 contains this text in src/consensus/validation.h.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/consensus/validation.h | grep -nF 'weight = (stripped_size * 4) + witness_size formula'Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 2/2, code 2/2History, hash and citation
Because a SegWit transaction's signatures sit in the witness, which the txid does not cover, changing how the transaction was signed no longer changes its txid; BIP 141 states this prevents involuntary malleability for any type of script as long as all inputs are signed.11: open 2 sources
How it worksBuilderEstablishedMedium confidence
T1BIP 141, Segregated Witness (Consensus layer)BIP, says this directly
changes to how the transaction was signed are no longer relevant to transaction identification.
Motivation, read 2026-11-20
T1BIP 141, Segregated Witness (Consensus layer)BIP, says this directly
It prevents involuntary transaction malleability for any type of scripts, as long as all inputs are signed
Motivation, read 2026-11-20
Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 2/2History, hash and citation
BIP 141 presents SegWit's malleability fix as what allows chains of unconfirmed transactions to be built without trusting the counterparty, a building block it names for payment networks such as the Lightning Network.12: open 2 sources
FactBuilderEstablishedMedium confidence
T1BIP 141, Segregated Witness (Consensus layer)BIP, says this directly
which enables the building of unconfirmed transaction dependency chains in a trust-free manner.
Motivation, read 2026-11-20
T1BIP 141, Segregated Witness (Consensus layer)BIP, says this directly
such as duplex micropayment channel and the Lightning Network, which have the potential to greatly improve
Motivation, read 2026-11-20
Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 2/2History, hash and citation
The Lightning specification (BOLT 3) requires a channel's funding output to be a SegWit pay-to-witness-script-hash (P2WSH) output locking a 2-of-2 multisignature script of the two parties' funding keys.13: open 2 sources
FactBuilderEstablishedMedium confidence
T1BOLT 3, Bitcoin Transaction and Script FormatsBOLT, says this directly
The funding output script is a P2WSH to:
Funding Transaction Output, read 2026-11-20
T1BOLT 3, Bitcoin Transaction and Script FormatsBOLT, says this directly
`2 <pubkey1> <pubkey2> 2 OP_CHECKMULTISIG`
Funding Transaction Output, read 2026-11-20
lightning/bolts at 191462825a contains this text in 03-transactions.md.
Run it yourself
git clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:03-transactions.md | grep -nF 'The funding output script is a P2WSH to:'Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 2/2, code 1/1History, hash and citation
In BIP 141, an output script (or P2SH redeem script) made of a 1-byte push opcode from OP_0 to OP_16 followed by a single direct data push of 2 to 40 bytes has a special meaning: the first push is the version byte and the pushed bytes are the witness program.14: open 2 sources
DefinitionBuilderEstablishedMedium confidence
T1BIP 141, Segregated Witness (Consensus layer)BIP, says this directly
followed by a direct data push between 2 and 40 bytes gets a new special meaning.
Specification, Witness program, read 2026-11-20
T1BIP 141, Segregated Witness (Consensus layer)BIP, says this directly
The following byte vector pushed is called the "witness program".
Specification, Witness program, read 2026-11-20
Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 2/2History, hash and citation
A version 0 witness program with a 20-byte program is a pay-to-witness-public-key-hash (P2WPKH) output and one with a 32-byte program is a pay-to-witness-script-hash (P2WSH) output; Bitcoin Core checks these sizes in VerifyWitnessProgram in src/script/interpreter.cpp.15: open 3 sources
TraceBuilderEstablishedHigh confidence
T1BIP 141, Segregated Witness (Consensus layer)BIP, says this directly
It is interpreted as a pay-to-witness-public-key-hash (P2WPKH) program.
Specification, Witness program, P2WPKH, read 2026-11-20
T1BIP 141, Segregated Witness (Consensus layer)BIP, says this directly
It is interpreted as a pay-to-witness-script-hash (P2WSH) program.
Specification, Witness program, P2WSH, read 2026-11-20
T1Bitcoin Core src/script/interpreter.cpp, VerifyWitnessProgramSource code, says this directly
} else if (program.size() == WITNESS_V0_KEYHASH_SIZE) {
VerifyWitnessProgram, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.h | grep -nF 'inline constexpr size_t WITNESS_V0_KEYHASH_SIZE = 20;'bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.h | grep -nF 'inline constexpr size_t WITNESS_V0_SCRIPTHASH_SIZE = 32;'bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.cpp.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.cpp | grep -nF 'if (program.size() == WITNESS_V0_SCRIPTHASH_SIZE) {'Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 3/3, code 3/3History, hash and citation
BIP 141 reserves witness versions 1 to 16 for future extensions and leaves their programs uninterpreted, so nodes that predate a new version accept its spends; later soft forks can then give a version new rules without breaking older nodes.16: open 4 sources
How it worksBuilderEstablishedHigh confidence
T1BIP 141, Segregated Witness (Consensus layer)BIP, says this directly
If the version byte is 1 to 16, no further interpretation of the witness program or witness stack happens,
Specification, Witness program, read 2026-11-20
T1BIP 141, Segregated Witness (Consensus layer)BIP, says this directly
These versions are reserved for future extensions.
Specification, Witness program, read 2026-11-20
T1BIP 141, Segregated Witness (Consensus layer)BIP, says this directly
programs with unknown versions are always considered as anyone-can-spend script
Motivation, script versioning, read 2026-11-20
T1Bitcoin Core src/script/interpreter.cpp, VerifyWitnessProgramSource code, says this directly
// Other version/size/p2sh combinations return true for future softfork compatibility
VerifyWitnessProgram, fallthrough for unknown versions, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.cpp | grep -nF '// Other version/size/p2sh combinations return true for future softfork compatibility'Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 4/4, code 1/1History, hash and citation
Taproot (BIP 341) defines rules for SegWit witness version 1: a Taproot output is a native SegWit output with witness version 1 and a 32-byte program, which Bitcoin Core checks in VerifyWitnessProgram.17: open 2 sources
TraceBuilderEstablishedHigh confidence
T1BIP 341, TaprootBIP, says this directly
A Taproot output is a native SegWit output
Specification, Script validation rules, read 2026-11-20
T1Bitcoin Core src/script/interpreter.cpp, VerifyWitnessProgramSource code, says this directly
} else if (witversion == 1 && program.size() == WITNESS_V1_TAPROOT_SIZE && !is_p2sh) {
VerifyWitnessProgram, witness version 1 branch, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.cpp | grep -nF '} else if (witversion == 1 && program.size() == WITNESS_V1_TAPROOT_SIZE && !is_p2sh) {'bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.h.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.h | grep -nF 'inline constexpr size_t WITNESS_V1_TAPROOT_SIZE = 32;'Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 2/2, code 2/2History, hash and citation
BIP 350 keeps the original Bech32 encoding for SegWit version 0 addresses (P2WPKH and P2WSH) and specifies a modified checksum, Bech32m, for addresses of witness version 1 and later, such as Taproot addresses.18: open 3 sources
FactBuilderEstablishedHigh confidence
T1BIP 350, Bech32m format for v1+ witness addressesBIP, says this directly
Bech32 remains in use for segregated witness outputs of version 0.
Abstract, read 2026-11-20
T1BIP 173, Base32 address format for native v0-16 witness outputsBIP, says this directly
BIP-350 proposes using the scheme described in this BIP only for Native Segwit v0 outputs.
Disclosures, read 2026-11-20
T2Bitcoin Optech topic, Bech32(m)Bitcoin Optech, says this directly
It is expected that bech32m will be used for taproot and future segwit-based script upgrades,
Topic description, read 2026-11-20
Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 3/3History, hash and citation
The specificationsBuilder
BIP 143 defines a new signature hash for SegWit version 0 inputs that reduces redundant hashing during verification, avoiding legacy signature hashing's quadratic growth, and that commits to the input amount; Bitcoin Core implements it in SignatureHash for SigVersion::WITNESS_V0.19: open 3 sources
TraceBuilderEstablishedHigh confidence
T1BIP 143, Transaction Signature Verification for Version 0 Witness ProgramBIP, says this directly
in order to minimize redundant data hashing in verification,
Abstract, read 2026-11-20
T1BIP 143, Transaction Signature Verification for Version 0 Witness ProgramBIP, supports part of it
as the number of sigops in a transaction increases.
Motivation, read 2026-11-20
T1Bitcoin Core src/script/interpreter.cpp, SignatureHashSource code, says this directly
if (sigversion == SigVersion::WITNESS_V0) {
SignatureHash, witness v0 branch, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.cpp | grep -nF 'hashPrevouts = cacheready ? cache->hashPrevouts : SHA256Uint256(GetPrevoutsSHA256(txTo));'BIP 143's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0143.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 3/3, code 2/2History, hash and citation
BIP 144 specifies how SegWit data travels between nodes: an extended transaction serialization with a zero marker byte and a nonzero flag byte, new getdata types for requesting witness data, and a service bit with which a node signals it can serve witnesses.20: open 3 sources
FactBuilderEstablishedMedium confidence
T1BIP 144, Segregated Witness (Peer Services)BIP, says this directly
This BIP defines new messages and serialization formats for propagation of transactions and blocks
Abstract, read 2026-11-20
T1BIP 144, Segregated Witness (Peer Services)BIP, says this directly
The marker byte is set to zero so that this structure will never parse as a valid transaction
Specification, Serialization, marker, read 2026-11-20
T1BIP 144, Segregated Witness (Peer Services)BIP, says this directly
A node will signal that it can provide witnesses using the following service bit
Handshake, read 2026-11-20
BIP 144's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0144.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 3/3, code 1/1History, hash and citation
BIP 145 updates the getblocktemplate JSON-RPC call that mining software uses so that block templates support SegWit, including a block weight limit field and a per-transaction weight field.21: open 2 sources
FactBuilderEstablishedMedium confidence
T1BIP 145, getblocktemplate Updates for Segregated WitnessBIP, says this directly
This BIP describes modifications to the getblocktemplate JSON-RPC call
Abstract, read 2026-11-20
T1BIP 145, getblocktemplate Updates for Segregated WitnessBIP, says this directly
numeric weight of the transaction, as counted for purposes of the block's weightlimit;
Block template, transactions, weight, read 2026-11-20
BIP 145's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0145.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 2/2, code 1/1History, hash and citation
In the codeResearcher
A SegWit block commits to its witness data through a commitment in an output script of its coinbase transaction; Bitcoin Core verifies it in CheckWitnessMalleation in src/validation.cpp and rejects a mismatching block with the reason "bad-witness-merkle-match".22: open 2 sources
TraceResearcherEstablishedHigh confidence
T1BIP 141, Segregated Witness (Consensus layer)BIP, supports part of it
of the coinbase transaction.
Specification, Commitment structure, read 2026-11-20
T1Bitcoin Core src/validation.cpp, CheckWitnessMalleationSource code, says this directly
static bool CheckWitnessMalleation(const CBlock& block, bool expect_witness_commitment, BlockValidationState& state)
CheckWitnessMalleation, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/validation.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/validation.cpp | grep -nF '/*reject_reason=*/"bad-witness-merkle-match",'Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 2/2, code 1/1History, hash and citation
In Bitcoin Core's VerifyWitnessProgram, when the SCRIPT_VERIFY_DISCOURAGE_UPGRADABLE_WITNESS_PROGRAM flag is set, a spend of a witness program with a not-yet-defined version fails with an error instead of succeeding as it does under consensus rules alone.23: open 1 source
How it worksResearcherEstablishedMedium confidence
T1Bitcoin Core src/script/interpreter.cpp, VerifyWitnessProgramSource code, says this directly
return set_error(serror, SCRIPT_ERR_DISCOURAGE_UPGRADABLE_WITNESS_PROGRAM);
VerifyWitnessProgram, unknown witness versions, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/script/interpreter.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/script/interpreter.cpp | grep -nF 'if (flags & SCRIPT_VERIFY_DISCOURAGE_UPGRADABLE_WITNESS_PROGRAM) {'Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 1/1, code 1/1History, hash and citation
Bitcoin Core PR #16060, merged on 15 August 2019, replaced SegWit's BIP 9 deployment logic with a hardcoded activation height ("burying" the deployment); as of block 976,753, Bitcoin Core's mainnet parameters carry SegwitHeight = 481824 rather than version-bits parameters for SegWit.24: open 2 sources
TraceResearcherEstablishedHigh confidence
T1Bitcoin Core PRPull request, says this directly
This hardcodes CSV and segwit activation heights, similar to the BIP 90 buried deployments for BIPs 34, 65 and 66.
PR description, read 2026-11-20
T1Bitcoin Core src/kernel/chainparams.cpp, CMainParamsSource code, says this directly
consensus.SegwitHeight = 481824; // 0000000000000000001c8018d9cb3b742ef25114f27563e3fc4a1902167f9893
CMainParams, consensus.SegwitHeight, 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 yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/kernel/chainparams.cpp | grep -nF 'consensus.SegwitHeight = 481824;'Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 2/2, code 1/1History, hash and citation
Deployment historyResearcher
The SegWit implementation entered Bitcoin Core's master branch through PR #8149, "Segregated witness rebased", a rebased and squashed version of PR #7910, merged on 24 June 2016 and later shipped with mainnet deployment parameters in Bitcoin Core 0.13.1.25: open 2 sources
EventResearcherEstablishedMedium confidence
T1Bitcoin Core PRPull request, says this directly
This PR is a rebased and squashed version of
PR description, read 2026-11-20
T1Bitcoin Core 0.13.1 release notes, Segregated witness soft forkRelease notes, supports part of it
Activation for the segwit soft fork is being managed using BIP9 versionbits.
Notable changes, Segregated witness soft fork, read 2026-11-20
Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 2/2History, hash and citation
SegWit was deployed with BIP 9 version bits on bit 1, with a mainnet signaling window from 15 November 2016 to 15 November 2017: if 95% of blocks in a 2,016-block retarget period signaled, it would lock in, and activate 2,016 blocks later.26: open 5 sources
FactResearcherEstablishedHigh confidence
T1BIP 141, Segregated Witness (Consensus layer)BIP, says this directly
This BIP will be deployed by "version bits" BIP9 with the name "segwit" and using bit 1.
Deployment, read 2026-11-20
T1BIP 141, Segregated Witness (Consensus layer)BIP, says this directly
For Bitcoin mainnet, the BIP9 starttime will be midnight 15 November 2016 UTC (Epoch timestamp 1479168000)
Deployment, read 2026-11-20
T1Bitcoin Core 0.13.1 release notes, Segregated witness soft forkRelease notes, says this directly
If 95% of blocks within a 2,016-block retarget period (about two weeks) signal support for segwit,
Notable changes, Segregated witness soft fork, activation, read 2026-11-20
T1Bitcoin Core 0.13.1 release notes, Segregated witness soft forkRelease notes, says this directly
After another 2,016 blocks, segwit will activate.
Notable changes, Segregated witness soft fork, activation, read 2026-11-20
T2Bitcoin Optech topic, Soft fork activationBitcoin Optech, says this directly
The segwit soft fork was released with BIP9 activation parameters.
History, 2016 to 2017, read 2026-11-20
BIP 141's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0141.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 5/5, code 1/1History, hash and citation
According to Bitcoin Optech's account of the 2017 deployment, BIP 91 locked in and activated first, SegWit's own BIP 9 deployment then locked in and activated, and BIP 148's mandatory signaling expired when SegWit locked in.27: open 2 sources
EventResearcherEstablishedMedium confidence
T2Bitcoin Optech topic, Soft fork activationBitcoin Optech, says this directly
BIP91 locked in and activated.
History, 2016 to 2017, read 2026-11-20
T1BIP 148, Mandatory activation of segwit deploymentBIP, supports part of it
This BIP will cease to be active when segwit is locked-in.
Specification, read 2026-11-20
Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 2/2History, hash and citation
How much did each 2017 event, including BIP 148 and BIP 91, contribute to SegWit's activation? Bitcoin Optech describes this as remaining "a subject of debate"; the chain records which blocks signaled, but not why their miners chose to signal.28: open 1 source
Open questionResearcherEstablishedMedium confidence
T2Bitcoin Optech topic, Soft fork activationBitcoin Optech, says this directly
It remains a subject of debate exactly how much each of the above events, and other events occurring around the
History, 2016 to 2017, closing paragraph, read 2026-11-20
Checked at block 976,753, 20 Nov 2026, 16:42 UTC: quotes 1/1History, hash and citation