summaryrefslogtreecommitdiff
path: root/bip-0174.mediawiki
diff options
context:
space:
mode:
authorSanket Kanjalkar <sanket1729@gmail.com>2020-08-04 13:27:31 -0500
committerGitHub <noreply@github.com>2020-08-04 13:27:31 -0500
commit8d3b41936f061fb1e86917f9f6f33182a277b42c (patch)
tree9edf57ce496c10d1a74af005f05dff4289e759ae /bip-0174.mediawiki
parentb4dddbcf75c47cdb02643d5f70f9f5054ab7b6b0 (diff)
downloadbips-8d3b41936f061fb1e86917f9f6f33182a277b42c.tar.xz
Fix formatting changes
Diffstat (limited to 'bip-0174.mediawiki')
-rw-r--r--bip-0174.mediawiki2
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0174.mediawiki b/bip-0174.mediawiki
index 445e350..43ffcdf 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>