BIP 0141 - Revision history

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/49ec00afae54b54b/bip-0141.mediawiki

2024-04-26T23:08:25Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/49ec00afae54b54b/bip-0141.mediawiki

← Older revision		Revision as of 23:08, 26 April 2024
Line 87:		Line 87:
	=== Witness program ===		=== Witness program ===

	A <code>scriptPubKey</code> (or <code>redeemScript</code> as defined in BIP16/P2SH) that consists of a ~~select subset~~ of ~~opcodes (~~<code>OP_0,OP_1,OP_2,...,OP_16</code>) followed by a data push between 2 and 40 bytes gets a new special meaning. The value of the first push is called the "version byte". The following byte vector pushed is called the "witness program".		A <code>scriptPubKey</code> (or <code>redeemScript</code> as defined in BIP16/P2SH) that consists of a 1-byte push opcode (one of <code>OP_0,OP_1,OP_2,...,OP_16</code>) followed by a direct data push between 2 and 40 bytes gets a new special meaning. The value of the first push is called the "version byte". The following byte vector pushed is called the "witness program".
			In more detail, this means a <code>scriptPubKey</code> or <code>redeemScript</code> which consists of (in order):
			* First, byte 0x00 (<code>OP_0</code>) or any byte between 0x51 (<code>OP_1</code>) and 0x60 (<code>OP_16</code>) inclusive (the version byte).
			* Then, a byte ''L'' between 0x02 (push of 2 bytes) and 0x28 (push of 40 bytes) inclusive.
			* Finally, ''L'' arbitrary bytes (the witness program).

	There are two cases in which witness validation logic are triggered. Each case determines the location of the witness version byte and program, as well as the form of the scriptSig:		There are two cases in which witness validation logic are triggered. Each case determines the location of the witness version byte and program, as well as the form of the scriptSig:
Line 93:		Line 97:
	# Triggered when a <code>scriptPubKey</code> is a P2SH script, and the BIP16 <code>redeemScript</code> pushed in the <code>scriptSig</code> is exactly a push of a version byte plus a push of a witness program. The <code>scriptSig</code> must be exactly a push of the BIP16 <code>redeemScript</code> or validation fails. (''"P2SH witness program"'')		# Triggered when a <code>scriptPubKey</code> is a P2SH script, and the BIP16 <code>redeemScript</code> pushed in the <code>scriptSig</code> is exactly a push of a version byte plus a push of a witness program. The <code>scriptSig</code> must be exactly a push of the BIP16 <code>redeemScript</code> or validation fails. (''"P2SH witness program"'')

	If the version byte is 0, and the witness program is 20 bytes:		If the version byte is 0, and the witness program is 20 bytes (''L = 20''):
	* It is interpreted as a pay-to-witness-public-key-hash (P2WPKH) program.		* It is interpreted as a pay-to-witness-public-key-hash (P2WPKH) program.
	* The witness must consist of exactly 2 items (≤ 520 bytes each). The first one a signature, and the second one a public key.		* The witness must consist of exactly 2 items (≤ 520 bytes each). The first one a signature, and the second one a public key.
Line 99:		Line 103:
	* After normal script evaluation, the signature is verified against the public key with CHECKSIG operation. The verification must result in a single TRUE on the stack.		* After normal script evaluation, the signature is verified against the public key with CHECKSIG operation. The verification must result in a single TRUE on the stack.

	If the version byte is 0, and the witness program is 32 bytes:		If the version byte is 0, and the witness program is 32 bytes (''L = 32''):
	* It is interpreted as a pay-to-witness-script-hash (P2WSH) program.		* It is interpreted as a pay-to-witness-script-hash (P2WSH) program.
	* The witness must consist of an input stack to feed to the script, followed by a serialized script (<code>witnessScript</code>).		* The witness must consist of an input stack to feed to the script, followed by a serialized script (<code>witnessScript</code>).

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/979ee894b8a4a2e9/bip-0141.mediawiki

2024-04-23T21:43:32Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/979ee894b8a4a2e9/bip-0141.mediawiki

← Older revision		Revision as of 21:43, 23 April 2024
Line 280:		Line 280:
	Since a version byte is pushed before a witness program, and programs with unknown versions are always considered as anyone-can-spend script, it is possible to introduce any new script system with a soft fork. The witness as a structure is not restricted by any existing script semantics and constraints, the 520-byte push limit in particular, and therefore allows arbitrarily large scripts and signatures.		Since a version byte is pushed before a witness program, and programs with unknown versions are always considered as anyone-can-spend script, it is possible to introduce any new script system with a soft fork. The witness as a structure is not restricted by any existing script semantics and constraints, the 520-byte push limit in particular, and therefore allows arbitrarily large scripts and signatures.

	Examples of new script ~~system~~ include Schnorr signatures which reduce the size of multisig transactions dramatically, ~~Lamport signature~~ which is quantum computing ~~resistance,~~ and Merklized abstract syntax trees which allow very compact ~~witness~~ for conditional scripts with extreme complexity.		Examples of new script systems include Schnorr signatures, which reduce the size of multisig transactions dramatically; Lamport signatures, which are quantum computing resistant; and Merklized abstract syntax trees, which allow very compact witnesses for conditional scripts with extreme complexity.

	=== Per-input lock-time and relative-lock-time ===		=== Per-input lock-time and relative-lock-time ===
Line 307:		Line 307:
	This BIP will be deployed by "version bits" BIP9 with the name "segwit" and using bit 1.		This BIP will be deployed by "version bits" BIP9 with the name "segwit" and using bit 1.

	For Bitcoin mainnet, the BIP9 starttime will be midnight 15 ~~november~~ 2016 UTC (Epoch timestamp 1479168000) and BIP9 timeout will be midnight 15 ~~november~~ 2017 UTC (Epoch timestamp 1510704000).		For Bitcoin mainnet, the BIP9 starttime will be midnight 15 November 2016 UTC (Epoch timestamp 1479168000) and BIP9 timeout will be midnight 15 November 2017 UTC (Epoch timestamp 1510704000).

	For Bitcoin testnet, the BIP9 starttime will be midnight 1 May 2016 UTC (Epoch timestamp 1462060800) and BIP9 timeout will be midnight 1 May 2017 UTC (Epoch timestamp 1493596800).		For Bitcoin testnet, the BIP9 starttime will be midnight 1 May 2016 UTC (Epoch timestamp 1462060800) and BIP9 timeout will be midnight 1 May 2017 UTC (Epoch timestamp 1493596800).

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/4731fc407f0c320b/bip-0141.mediawiki

2024-04-23T20:13:27Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/4731fc407f0c320b/bip-0141.mediawiki

← Older revision		Revision as of 20:13, 23 April 2024
Line 87:		Line 87:
	=== Witness program ===		=== Witness program ===

	A <code>scriptPubKey</code> (or <code>redeemScript</code> as defined in BIP16/P2SH) that consists of a ~~1-byte push opcode~~ (~~for 0 to 16~~) followed by a data push between 2 and 40 bytes gets a new special meaning. The value of the first push is called the "version byte". The following byte vector pushed is called the "witness program".		A <code>scriptPubKey</code> (or <code>redeemScript</code> as defined in BIP16/P2SH) that consists of a select subset of opcodes (<code>OP_0,OP_1,OP_2,...,OP_16</code>) followed by a data push between 2 and 40 bytes gets a new special meaning. The value of the first push is called the "version byte". The following byte vector pushed is called the "witness program".

	There are two cases in which witness validation logic are triggered. Each case determines the location of the witness version byte and program, as well as the form of the scriptSig:		There are two cases in which witness validation logic are triggered. Each case determines the location of the witness version byte and program, as well as the form of the scriptSig:

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/43da5dec5eaf0d81/bip-0141.mediawiki

2022-08-04T12:02:04Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/43da5dec5eaf0d81/bip-0141.mediawiki

← Older revision		Revision as of 12:02, 4 August 2022
Line 60:		Line 60:
	The <code>flag</code> MUST be a 1-byte non-zero value. Currently, <code>0x01</code> MUST be used.		The <code>flag</code> MUST be a 1-byte non-zero value. Currently, <code>0x01</code> MUST be used.

	The <code>witness</code> is a serialization of all witness ~~data~~ of the transaction. Each txin is associated with a witness field. A witness field starts with a <code>var_int</code> to indicate the number of stack items for the txin. It is followed by stack items, with each item starts with a <code>var_int</code> to indicate the length. Witness data is NOT script.		The <code>witness</code> is a serialization of all witness fields of the transaction. Each txin is associated with a witness field. A witness field starts with a <code>var_int</code> to indicate the number of stack items for the txin. It is followed by stack items, with each item starts with a <code>var_int</code> to indicate the length. Witness data is NOT script.

	A non-witness program (defined hereinafter) txin MUST be associated with an empty witness field, represented by a <code>0x00</code>. If all txins are not witness program, a transaction's <code>wtxid</code> is equal to its <code>txid</code>.		A non-witness program (defined hereinafter) txin MUST be associated with an empty witness field, represented by a <code>0x00</code>. If all txins are not witness program, a transaction's <code>wtxid</code> is equal to its <code>txid</code>.

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/19c429ee2831d898/bip-0141.mediawiki

2021-02-12T21:20:14Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/19c429ee2831d898/bip-0141.mediawiki

← Older revision		Revision as of 21:20, 12 February 2021
Line 131:		Line 131:
	The sigop limit is likewise quadrupled to ≤ 80,000.		The sigop limit is likewise quadrupled to ≤ 80,000.

	Each P2WPKH input is counted as 1 sigop. In addition, opcodes within a P2WSH <code>witnessScript</code> are counted identically as previously within the P2SH <code>redeemScript</code>. That is, CHECKSIG is counted as only 1 sigop~~, and~~ CHECKMULTISIG is counted as 1 to 20 sigops ~~according to the arguments~~. This rule applies to both native witness program and P2SH witness program.		Each P2WPKH input is counted as 1 sigop. In addition, opcodes within a P2WSH <code>witnessScript</code> are counted identically as previously within the P2SH <code>redeemScript</code>. That is, CHECKSIG is counted as only 1 sigop. When preceded by OP_1 to OP_16 CHECKMULTISIG is counted as 1 to 16 sigops respectively, otherwise it is counted as 20 sigops. This rule applies to both native witness program and P2SH witness program.

	=== Additional definitions ===		=== Additional definitions ===

934: Update BIP text with latest version from https://github.com/bitcoin/bips/blob/b5723035e23896d0/bip-0141.mediawiki

2019-09-24T17:58:35Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/b5723035e23896d0/bip-0141.mediawiki

Show changes

Spaz926: Created page with "{{bip}}

   BIP: 141   Title: Segregated Witness (Consensus layer)   Authors: Eric Lombrozo            Johnson Lau            Pieter W..."

2016-02-12T03:21:12Z

Created page with "{{bip}} <pre> BIP: 141 Title: Segregated Witness (Consensus layer) Authors: Eric Lombrozo <elombrozo@gmail.com> Johnson Lau <jl2012@xbt.hk> Pieter W..."

New page

{{bip}}

<pre>
BIP: 141
Title: Segregated Witness (Consensus layer)
Authors: Eric Lombrozo <elombrozo@gmail.com>
Johnson Lau <jl2012@xbt.hk>
Pieter Wuille <pieter.wuille@gmail.com>
Status: Draft
Type: Standards Track
Created: 2015-12-21
</pre>

{{BipMoved|bip-0141.mediawiki}}