summaryrefslogtreecommitdiff
path: root/bip-0141.mediawiki
AgeCommit message (Collapse)Author
2024-07-25Remove trailing whitespace from all BIPsOrfeas Stefanos Thyfronitis Litos
2024-04-26Clarify exactly which scripts are witness outputsPieter Wuille
2024-04-23Fix grammarLucas Cullen
2024-04-23Fix typos in BIP141Murch
Co-authored-by: Greg Laun
2024-04-23Merge pull request #487 from Christewart/patch-2Mark "Murch" Erhardt
Specify which 1 byte push op codes are valid
2022-07-14bip-141: `witness` field wording improvement志宇
When describing the `witness` field, reword "witness data" to "witness field" as "witness data" refers also to the `marker` and `flag` fields.
2021-01-11bip-0141: clarify the sigop count calculation for CHECKMULTISIGAntoine Poinsot
Since the sigOpCount calculation was copied from P2SH, and P2SH restricts the use of CHECKMULTISIG with pushed integers the reference implementation would not take into account the number of public keys for 17 to 20 keys (not representable with an OP_N) even for P2WSH. Therefore it fallbacks to accounting for 20 sigops in this case, which this sentence seemed to mismatch with. Btcd and Libbitcoin use the same calculation as in Bitcoin Core. Signed-off-by: Antoine Poinsot <darosior@protonmail.com>
2018-03-10BIP141: Add BIP173 to references.Jonathan Cross
2018-02-12Merge remote-tracking branch 'origin-pull/584/head'Luke Dashjr
2017-10-29Update status of BIPs 141, 143, 144, and 147 to ProposedLuke Dashjr
2017-09-22is->are in BIP 141danra
2017-09-17Update status for segwit related BIPsJohnson Lau
2017-01-03Update bip-0141.mediawikiChris Stewart
Clarifying rewording, `OP_0` is not a 1 byte push op code since it pushes the empty byte vector onto the stack.
2017-01-03Specify which 1 byte push op codes are validChris Stewart
This adds documentation to BIP141 about which 1 byte push op codes are valid for segwit. This is needed because `OP_1NEGATE` is a 1 byte push op code, but is NOT a valid 1 byte push op code for segwit. See the implementation here for why `OP_1NEGATE` is not valid: https://github.com/bitcoin/bitcoin/blob/14d01309bed59afb08651f2b701ff90371b15b20/src/script/script.cpp#L228
2016-11-30Promote BIP 2 Draft->Active, and implement itLuke Dashjr
- Update all Accepted status to Proposed (renamed status) - The BIP Comments preamble headers added to every BIP - The License preamble headers have been added to all BIPs with a Copyright section
2016-11-30Promote BIP 123 Draft->Active, and implement itLuke Dashjr
2016-10-17BIP 141 start and end timePieter Wuille
2016-10-05Add policy descriptions to BIP141 and 143 and address some nits.Johnson Lau
2016-09-16Update BIP 141 to include definition of Virtual transaction size and ↵jonnynewbs
Transaction weight
2016-07-25Link to permanent PR of reference implementationJanus Troelsen
analogue to https://github.com/bitcoin/bips/commit/ecfb7ebbca3488cd4c1e11210cbc5914a9228c67
2016-07-21Merge pull request #416 from jl2012/patch-26Luke-Jr
BIP141 fix
2016-07-19BIP141 terms fixjl2012
2016-07-18bip141: Change 'block cost' to 'block weight'Wladimir J. van der Laan
The term 'block cost' led to confusion about the unit that it is expressed in, in that it expressed monetary cost. Change it to a more general term 'block weight'. This was discussed in the [2016-07-14 Bitcoin Core developer meeting](http://www.erisian.com.au/meetbot/bitcoin-core-dev/2016/bitcoin-core-dev.2016-07-14-19.00.html).
2016-07-16Merge pull request #399 from jl2012/patch-22Luke-Jr
BIP141 script failure clarifications
2016-07-12bip141: clarify that marker is 1 byteDaniel Cousens
2016-06-10BIP141: clarify size restriction for witness stackJohnson Lau
2016-06-07BIP141 script failure clarificationsJohnson Lau
Footnotes to clarify some special conditions which witness scripts will fail
2016-06-04BIP141: extend max witness program size to 40 bytesJohnson Lau
The maximum witness program size is increased from 32 to 40 bytes. This provides extra space to specify script version (for originally 16 upgradable versions to up to 16 * 2 ^ 64)
2016-05-15Merge remote-tracking branch 'origin/master' into segwit_gbt_updates_20160330Luke Dashjr
2016-05-06BIP141: BIP9 parameters for testnetJohnson Lau
2016-04-26BIP141 clarifications and formattingJohnson Lau
Add rationale of block cost Change the name of "witness nonce" to "witness reserved value" Update link to reference implementation Formatting
2016-04-23Merge remote-tracking branch 'personal-github/segwit_gbt_updates_20160330' ↵Luke Dashjr
into segwit_gbt_updates_20160330
2016-04-23Merge branch 'master' into segwit_gbt_updates_20160330Luke Dashjr
2016-04-23BIP141: Block cost clrificationjl2012
2016-04-23Add P2SH-P2WPKH examplejl2012
2016-04-22Update bip-0141.mediawikiAaron Voisine
The byte representation of "<0 <32-byte-hash>>" is "0x220020{32-byte-hash}" What was listed here would be the byte representation of "0 <32-byte-hash>". The text explains that there is only one item in scriptSig, so I'm guessing the byte representation is wrong. Also the corrected byte representation would produce the same sig/pubkey described in P2WSH after following the bip16 rules.
2016-04-09BIP141: commitment clarification. BIP144: new diagramjl2012
2016-04-05Update bip-0141.mediawikiJohnson Lau
2016-03-31Clarify what remains "to be decided"฿tcDrak
2016-03-31BIP141: Sigop clarificationJohnson Lau
2016-03-30BIP 141: Specify VB nameLuke Dashjr
2016-03-30BIP 141 & 145: Clarify sigop interactionLuke Dashjr
2016-03-25Witness validation logic trigger clarificationsEric Lombrozo
2016-03-21Remove deployment section.฿tcDrak
Now we know we will use BIP9 version bits, remove references to ISM() and leave TDB as was done with BIP68,112 and 113.
2016-01-29Merge pull request #303 from jl2012/patch-10Luke-Jr
BIP141: Add 520 bytes witness stack limit
2016-01-29Merge pull request #300 from afk11/typo-141Luke-Jr
BIP141, fix small typo
2016-01-26BIP141: Add 520 bytes witness stack limitJohnson Lau
@sipa
2016-01-26BIP141 Non-upgraded wallet descriptionJohnson Lau
2016-01-24Merge pull request #295 from fanatid/fix/bip141-urlsLuke-Jr
BIP 141: fix URLs
2016-01-24typoThomas Kerin