2026-11-20-seed-segwit
Published
29 claims
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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).
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- Segregated Witness (SegWit) is a Bitcoin soft fork, activated in 2017, that moves the signature data of a transaction (its "witness") into a separate structure that blocks commit to apart from the transaction data that the transaction ID covers.
- 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".
- 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.
- 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.
- 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.
Held for the owner
Their text stays private until the owner approves it.
- 5 claims on segwit
names Eric Lombrozo, Johnson Lau, Pieter Wuille; an argument; names Shaolin Fry; names James Hilliard
Rejected
5 candidates
- SegWit's BIP 9 deployment locked in at block 479,808, on 9 August 2017.
research: No T1 or T2 source fetched in this run states the lock-in height; it follows arithmetically (481,824 minus 2,016) but only media, a gist and a blocked learnmeabitcoin page carried it.
- BIP 91 locked in at block 477,120 and activated around 23 July 2017.
research: Only media sources and an explorer page; no primary or T2 source fetched.
- The New York Agreement and SegWit2x proposal and its withdrawal.
research: Out of scope for this seed and contested; would need primary statements from signatories and opponents.
- Most wallets default to SegWit addresses.
research: No count or method; replaced by the dated Bitcoin Core default.
- BIP 141 block weight rule quoted directly from the BIP.
research: The raw mediawiki line wraps terms in '' markup; cited the code comment instead, BIP only partially.
Could not settle
- The exact lock-in height and dates for BIP 91 and SegWit's own deployment need a primary or T2 source; a Bitcoin Stack Exchange answer (API unreachable this run) or reading version-bit state from a node (getdeploymentinfo at heights 479,807 and 479,808) would settle them.
- The witness discount's rationale and its critics (for example data embedding in witnesses) are not covered; that needs attributed argument claims from mailing-list posts with message ids.
- Several BIP quotes come from raw mediawiki; if the checker does not strip markup, the BIP 141 "≤ 4,000,000." and BIP 173 lowercase quotes are the most likely to need adjustment.
- BIP 148's preamble shows Status Deployed at this commit; whether that reflects a BIP 3 status migration was not investigated, so no bip.field check was added for it.
Injection attempts
No text in any source this run read tried to give the brain orders.
Read
30 sources
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0141.mediawiki
weight, witness program, versions, txid and wtxid, malleability, Lightning motivation, deployment parameters, authors
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0143.mediawiki
new signature hash, input amount commitment, cold wallet motivation
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0144.mediawiki
peer services, marker and flag, service bit
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0145.mediawiki
getblocktemplate changes
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0173.mediawiki
Bech32, examples, error detection, BIP 350 disclosure
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0350.mediawiki
Bech32m for witness version 1 and later
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0341.mediawiki
Taproot as witness version 1
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0009.mediawiki
version bits background (not cited; quotes contained markup)
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0091.mediawiki
BIP 91 parameters, motivation, author
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0148.mediawiki
BIP 148 parameters, motivation, author
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/kernel/chainparams.cpp
SegwitHeight with hash comment, bech32 hrp
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/consensus/consensus.h
MAX_BLOCK_WEIGHT, WITNESS_SCALE_FACTOR
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/consensus/validation.h
weight formula comment and GetTransactionWeight
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/script/interpreter.cpp
VerifyWitnessProgram, SignatureHash witness v0 branch
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/script/interpreter.h
witness program size constants
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/validation.cpp
CheckWitnessMalleation and reject reasons
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/wallet/wallet.h
DEFAULT_ADDRESS_TYPE
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/doc/release-notes/release-notes-0.13.1.md
SegWit deployment in 0.13.1
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/doc/release-notes/release-notes-0.20.0.md
default bech32 addresses
- https://raw.githubusercontent.com/lightning/bolts/191462825ae341f0a27098765c075f01ca9bc6c2/03-transactions.md
P2WSH funding output
- https://github.com/bitcoin/bitcoin/pull/8149
SegWit implementation PR
- https://github.com/bitcoin/bitcoin/pull/16060
burying the SegWit deployment
- https://mempool.space/api/block-height/481824
block hash at activation height
- https://mempool.space/api/block/0000000000000000001c8018d9cb3b742ef25114f27563e3fc4a1902167f9893
header time of block 481,824
- https://mempool.space/api/block-height/479808
hash of the first block of the presumed lock-in period (not used in a claim)
- https://bitcoinops.org/en/topics/segregated-witness/
Optech topic (a stub)
- https://bitcoinops.org/en/topics/soft-fork-activation/
2016 to 2017 deployment history, BIP 91 and BIP 148 outcome, debate over causes
- https://bitcoinops.org/en/topics/bech32/
Bech32 and Bech32m coverage
- https://bitcoinops.org/en/bech32-sending-support/
located the vbyte comparison; cited via the 16 April 2019 newsletter instead
- https://bitcoinops.org/en/newsletters/2019/04/16/
P2PKH versus P2WPKH spend sizes