diff options
author | Luke Dashjr <luke_github1@dashjr.org> | 2020-08-20 22:17:04 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-08-20 22:17:04 +0000 |
commit | 76c3ced4b074866ffd3ae7bd28dbb96dd4cadd8a (patch) | |
tree | 4b990f3acdc92e581845e60ccb3a41ffc62f2a13 | |
parent | f6e11640e76338fef2c728225d6a4fb9b0f77d67 (diff) | |
parent | 8d3b41936f061fb1e86917f9f6f33182a277b42c (diff) |
Merge pull request #964 from sanket1729/master
BIP 174: Fix formatting changes
-rw-r--r-- | bip-0174.mediawiki | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0174.mediawiki b/bip-0174.mediawiki index 08aec09..65fa9a9 100644 --- a/bip-0174.mediawiki +++ b/bip-0174.mediawiki @@ -143,7 +143,7 @@ The currently defined per-input types are defined as follows: * Type: Non-Witness UTXO <tt>PSBT_IN_NON_WITNESS_UTXO = 0x00</tt> ** Key: None. The key must only contain the 1 byte type. ***<tt>{0x00}</tt> -** Value: The transaction in network serialization format the current input spends from. This should be present for inputs that spend non-segwit outputs and can be present for inputs that spend segwit outputs. An input can have both <tt>PSBT_IN_NON_WITNESS_UTXO</tt> and <tt>PSBT_IN_WITNESS_UTXO</tt>. <ref>'''Why can both UTXO types be provided?''' Many wallets began requiring the full previous transaction (i.e. <tt>PSBT_IN_NON_WITNESS_UTXO</tt>) for segwit inputs when PSBT was already in use. In order to be compatible with software which were expecting <tt>PSBT_IN_WITNESS_UTXO<tt>, both UTXO types must be allowed.</ref> +** Value: The transaction in network serialization format the current input spends from. This should be present for inputs that spend non-segwit outputs and can be present for inputs that spend segwit outputs. An input can have both <tt>PSBT_IN_NON_WITNESS_UTXO</tt> and <tt>PSBT_IN_WITNESS_UTXO</tt>. <ref>'''Why can both UTXO types be provided?''' Many wallets began requiring the full previous transaction (i.e. <tt>PSBT_IN_NON_WITNESS_UTXO</tt>) for segwit inputs when PSBT was already in use. In order to be compatible with software which were expecting <tt>PSBT_IN_WITNESS_UTXO</tt>, both UTXO types must be allowed.</ref> *** <tt>{transaction}</tt> * Type: Witness UTXO <tt>PSBT_IN_WITNESS_UTXO = 0x01</tt> |