BIP 0174 - Revision history

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

2024-10-09T19:23:41Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/83a1afd985984862/bip-0174.mediawiki

@@ Line 486: / Line 486: @@
 | 0, 2
 | [[bip-0371.mediawiki|371]]
 |-
 | Proprietary Use Type
@@ Line 602: / Line 648: @@
 | 0, 2
 | [[bip-0371.mediawiki|371]]
 |-
 | Proprietary Use Type
@@ Line 825: / Line 897: @@
 Although some PSBT version 0 implementations encode types as uint8_t rather than compact size,
 it is still safe to add >0xFD fields to PSBT 0, because these old parsers ignore
 unknown fields, and <keytype> is prefixed by its length.
 ===Procedure For New Versions===

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

2024-04-30T21:38:40Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/51b2d131bea737bc/bip-0174.mediawiki

← Older revision		Revision as of 21:38, 30 April 2024
Line 637:		Line 637:

	For all global, per-input, and per-output maps, the type <tt>0xFC</tt> is reserved for proprietary use.		For all global, per-input, and per-output maps, the type <tt>0xFC</tt> is reserved for proprietary use.
	The proprietary use type requires keys that follow the type with a compact size unsigned integer representing the length of the string ~~identifer~~, followed by the string identifier, then a subtype, and finally any key data.		The proprietary use type requires keys that follow the type with a compact size unsigned integer representing the length of the string identifier, followed by the string identifier, then a subtype, and finally any key data.

	The identifier can be any variable length string that software can use to identify whether the particular data in the proprietary type can be used by it.		The identifier can be any variable length string that software can use to identify whether the particular data in the proprietary type can be used by it.

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

2024-04-30T20:08:02Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/2d9e431fbe654640/bip-0174.mediawiki

← Older revision		Revision as of 20:08, 30 April 2024
Line 804:		Line 804:

	The Partially Signed Transaction format can be extended in the future by adding		The Partially Signed Transaction format can be extended in the future by adding
	new types for key-value pairs. Backwards ~~compatibilty~~ will still be maintained as those new		new types for key-value pairs. Backwards compatibility will still be maintained as those new
	types will be ignored and passed-through by signers which do not know about them.		types will be ignored and passed-through by signers which do not know about them.

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

2023-12-14T05:13:42Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/9692c70eadc193d8/bip-0174.mediawiki

← Older revision		Revision as of 05:13, 14 December 2023
Line 6:		Line 6:
	Layer: Applications		Layer: Applications
	Title: Partially Signed Bitcoin Transaction Format		Title: Partially Signed Bitcoin Transaction Format
	Author: ~~Andrew~~ Chow <achow101~~@gmail~~.com>		Author: Ava Chow <me@achow101.com>
	Comments-Summary: No comments yet.		Comments-Summary: No comments yet.
	Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0174		Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0174

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

2023-03-08T05:12:09Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/4e4db8ba123aa8e9/bip-0174.mediawiki

← Older revision		Revision as of 05:12, 8 March 2023
Line 722:		Line 722:
	sign(non_witness_sighash(script_code, i, input))		sign(non_witness_sighash(script_code, i, input))

	for input,i in enumerate(psbt.inputs):		for input, i in enumerate(psbt.inputs):
	~~if non_witness_utxo.exists:~~		if witness_utxo.exists:
	~~assert(sha256d(non_witness_utxo) == psbt.tx.input[i].prevout.hash)~~
	~~if redeemScript.exists:~~
	~~assert(non_witness_utxo.vout[psbt.tx.input[i].prevout.n].scriptPubKey == P2SH(redeemScript))~~
	~~sign_non_witness(redeemScript, i)~~
	~~else:~~
	~~sign_non_witness(non_witness_utxo.vout[psbt.tx.input[i].prevout.n].scriptPubKey, i)~~
	~~else~~ if witness_utxo.exists:
	if redeemScript.exists:		if redeemScript.exists:
	assert(witness_utxo.scriptPubKey == P2SH(redeemScript))		assert(witness_utxo.scriptPubKey == P2SH(redeemScript))
Line 741:		Line 734:
	assert(script == P2WSH(witnessScript))		assert(script == P2WSH(witnessScript))
	sign_witness(witnessScript, i)		sign_witness(witnessScript, i)
			else if non_witness_utxo.exists:
			assert(sha256d(non_witness_utxo) == psbt.tx.input[i].prevout.hash)
			if redeemScript.exists:
			assert(non_witness_utxo.vout[psbt.tx.input[i].prevout.n].scriptPubKey == P2SH(redeemScript))
			sign_non_witness(redeemScript, i)
			else:
			sign_non_witness(non_witness_utxo.vout[psbt.tx.input[i].prevout.n].scriptPubKey, i)
	else:		else:
	assert False		assert False

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

2023-02-20T02:56:08Z

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

← Older revision		Revision as of 02:56, 20 February 2023
Line 457:		Line 457:
	\| <tt>PSBT_IN_TAP_BIP32_DERIVATION = 0x16</tt>		\| <tt>PSBT_IN_TAP_BIP32_DERIVATION = 0x16</tt>
	\| <tt><32 byte xonlypubkey></tt>		\| <tt><32 byte xonlypubkey></tt>
	\| A 32 byte X-only public key involved in this input. It may be the internal key, or a key present in a leaf script.		\| A 32 byte X-only public key involved in this input. It may be the output key, the internal key, or a key present in a leaf script.
	\| <tt><compact size uint number of hashes> <32 byte leaf hash>* <4 byte fingerprint> <32-bit little endian uint path element>*</tt>		\| <tt><compact size uint number of hashes> <32 byte leaf hash>* <4 byte fingerprint> <32-bit little endian uint path element>*</tt>
	\| A compact size unsigned integer representing the number of leaf hashes, followed by a list of leaf hashes, followed by the 4 byte master key fingerprint concatenated with the derivation path of the public key. The derivation path is represented as 32-bit little endian unsigned integer indexes concatenated with each other. Public keys are those needed to spend this output. The leaf hashes are of the leaves which involve this public key. The internal key does not have leaf hashes, so can be indicated with a <tt>hashes len</tt> of 0. Finalizers should remove this field after <tt>PSBT_IN_FINAL_SCRIPTWITNESS</tt> is constructed.		\| A compact size unsigned integer representing the number of leaf hashes, followed by a list of leaf hashes, followed by the 4 byte master key fingerprint concatenated with the derivation path of the public key. The derivation path is represented as 32-bit little endian unsigned integer indexes concatenated with each other. Public keys are those needed to spend this output. The leaf hashes are of the leaves which involve this public key. The internal key does not have leaf hashes, so can be indicated with a <tt>hashes len</tt> of 0. Finalizers should remove this field after <tt>PSBT_IN_FINAL_SCRIPTWITNESS</tt> is constructed.
Line 595:		Line 595:
	\| <tt>PSBT_OUT_TAP_BIP32_DERIVATION = 0x07</tt>		\| <tt>PSBT_OUT_TAP_BIP32_DERIVATION = 0x07</tt>
	\| <tt><32 byte xonlypubkey></tt>		\| <tt><32 byte xonlypubkey></tt>
	\| A 32 byte X-only public key involved in this output. It may be the internal key, or a key present in a leaf script.		\| A 32 byte X-only public key involved in this output. It may be the output key, the internal key, or a key present in a leaf script.
	\| <tt><compact size uint number of hashes> <32 byte leaf hash>* <4 byte fingerprint> <32-bit little endian uint path element>*</tt>		\| <tt><compact size uint number of hashes> <32 byte leaf hash>* <4 byte fingerprint> <32-bit little endian uint path element>*</tt>
	\| A compact size unsigned integer representing the number of leaf hashes, followed by a list of leaf hashes, followed by the 4 byte master key fingerprint concatenated with the derivation path of the public key. The derivation path is represented as 32-bit little endian unsigned integer indexes concatenated with each other. Public keys are those needed to spend this output. The leaf hashes are of the leaves which involve this public key. The internal key does not have leaf hashes, so can be indicated with a <tt>hashes len</tt> of 0. Finalizers should remove this field after <tt>PSBT_IN_FINAL_SCRIPTWITNESS</tt> is constructed.		\| A compact size unsigned integer representing the number of leaf hashes, followed by a list of leaf hashes, followed by the 4 byte master key fingerprint concatenated with the derivation path of the public key. The derivation path is represented as 32-bit little endian unsigned integer indexes concatenated with each other. Public keys are those needed to spend this output. The leaf hashes are of the leaves which involve this public key. The internal key does not have leaf hashes, so can be indicated with a <tt>hashes len</tt> of 0. Finalizers should remove this field after <tt>PSBT_IN_FINAL_SCRIPTWITNESS</tt> is constructed.

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

2023-02-10T00:00:45Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/30c88a4bec19b943/bip-0174.mediawiki

← Older revision		Revision as of 00:00, 10 February 2023
Line 124:		Line 124:
	\| None		\| None
	\| No key data		\| No key data
	\| <tt><32-bit little endian ~~uint~~ version></tt>		\| <tt><32-bit little endian int version></tt>
	\| The 32-bit little endian signed integer representing the version number of the transaction being created. Note that this is not the same as the PSBT version number specified by the PSBT_GLOBAL_VERSION field.		\| The 32-bit little endian signed integer representing the version number of the transaction being created. Note that this is not the same as the PSBT version number specified by the PSBT_GLOBAL_VERSION field.
	\| 2		\| 2

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

2023-01-18T03:00:25Z

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

← Older revision		Revision as of 03:00, 18 January 2023
Line 414:		Line 414:
	\| None		\| None
	\| No key data		\| No key data
	\| <tt><32-bit ~~uiht~~ locktime></tt>		\| <tt><32-bit uint locktime></tt>
	\| 32 bit unsigned little endian integer less than 500000000 representing the minimum block height that this input requires to be set as the transaction's lock time.		\| 32 bit unsigned little endian integer less than 500000000 representing the minimum block height that this input requires to be set as the transaction's lock time.
	\|		\|

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

2022-08-16T02:26:11Z

Update BIP text with latest version from https://github.com/bitcoin/bips/blob/64aba767e2d422b5/bip-0174.mediawiki

← Older revision		Revision as of 02:26, 16 August 2022
Line 680:		Line 680:
	Before signing a non-witness input, the Signer must verify that the TXID of the non-witness UTXO matches the TXID specified in the unsigned transaction.		Before signing a non-witness input, the Signer must verify that the TXID of the non-witness UTXO matches the TXID specified in the unsigned transaction.
	Before signing a witness input, the Signer must verify that the witnessScript (if provided) matches the hash specified in the UTXO or the redeemScript, and the redeemScript (if provided) matches the hash in the UTXO.		Before signing a witness input, the Signer must verify that the witnessScript (if provided) matches the hash specified in the UTXO or the redeemScript, and the redeemScript (if provided) matches the hash in the UTXO.
	The Signer may choose to fail to sign a segwit input if a non-witness UTXO is not provided. <ref>'''Why would non-witness UTXOs be provided for segwit inputs?''' The sighash algorithm for Segwit specified in BIP ~~173~~ is known to have an issue where an attacker could trick a user to sending Bitcoin to fees if they are able to convince the user to sign a malicious transaction multiple times. This is possible because the amounts in <tt>PSBT_IN_WITNESS_UTXO</tt> of other segwit inputs can be modified without effecting the signature for a particular input. In order to prevent this kind of attack, many wallets are requiring that the full previous transaction (i.e. <tt>PSBT_IN_NON_WITNESS_UTXO</tt>) be provided to ensure that the amounts of other inputs are not being tampered with.</ref>		The Signer may choose to fail to sign a segwit input if a non-witness UTXO is not provided. <ref>'''Why would non-witness UTXOs be provided for segwit inputs?''' The sighash algorithm for Segwit specified in BIP 143 is known to have an issue where an attacker could trick a user to sending Bitcoin to fees if they are able to convince the user to sign a malicious transaction multiple times. This is possible because the amounts in <tt>PSBT_IN_WITNESS_UTXO</tt> of other segwit inputs can be modified without effecting the signature for a particular input. In order to prevent this kind of attack, many wallets are requiring that the full previous transaction (i.e. <tt>PSBT_IN_NON_WITNESS_UTXO</tt>) be provided to ensure that the amounts of other inputs are not being tampered with.</ref>
	The Signer should not need any additional data sources, as all necessary information is provided in the PSBT format.		The Signer should not need any additional data sources, as all necessary information is provided in the PSBT format.
	The Signer must only add data to a PSBT.		The Signer must only add data to a PSBT.

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

2022-08-04T11:52:01Z

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

Show changes