summaryrefslogtreecommitdiff
path: root/bip-0370.mediawiki
diff options
context:
space:
mode:
authorSalvatore Ingala <6681844+bigspider@users.noreply.github.com>2023-03-04 11:24:05 +0000
committerSalvatore Ingala <6681844+bigspider@users.noreply.github.com>2023-03-04 11:24:05 +0000
commit5cf651155d8b7d2a53dd19084f299247ce03e5bc (patch)
tree550493de0e17bc08f61ca78edd85ac2ac44b9b10 /bip-0370.mediawiki
parentaa5b0a1009bcb90315ee6bdacc2592749d6d4636 (diff)
Relax transaction version requirement when the Creator is also a Constructor.
Diffstat (limited to 'bip-0370.mediawiki')
-rw-r--r--bip-0370.mediawiki4
1 files changed, 2 insertions, 2 deletions
diff --git a/bip-0370.mediawiki b/bip-0370.mediawiki
index b3f65ff..cb59801 100644
--- a/bip-0370.mediawiki
+++ b/bip-0370.mediawiki
@@ -235,9 +235,9 @@ PSBTv2 introduces new roles and modifies some existing roles.
===Creator===
In PSBTv2, the Creator initializes the PSBT with 0 inputs and 0 outputs.
-The PSBT version number is set to 2. The transaction version number must be set to at least 2. <ref>'''Why does the transaction version number need to be at least 2?''' The transaction version number is part of the validation rules for some features such as OP_CHECKSEQUENCEVERIFY. Since it is backwards compatible, and there are other ways to disable those features (e.g. through sequence numbers), it is easier to require transactions be able to support these features than to try to negotiate the transaction version number.</ref>
+The PSBT version number is set to 2.
The Creator should also set PSBT_GLOBAL_FALLBACK_LOCKTIME.
-If the Creator is not also a Constructor and will be giving the PSBT to others to add inputs and outputs, the PSBT_GLOBAL_TX_MODIFIABLE field must be present and and the Inputs Modifiable and Outputs Modifiable flags set appropriately.
+If the Creator is not also a Constructor and will be giving the PSBT to others to add inputs and outputs, the PSBT_GLOBAL_TX_MODIFIABLE field must be present and the Inputs Modifiable and Outputs Modifiable flags set appropriately; moreover, the transaction version number must be set to at least 2. <ref>'''Why does the transaction version number need to be at least 2?''' The transaction version number is part of the validation rules for some features such as OP_CHECKSEQUENCEVERIFY. Since it is backwards compatible, and there are other ways to disable those features (e.g. through sequence numbers), it is easier to require transactions be able to support these features than to try to negotiate the transaction version number.</ref>
If the Creator is a Constructor and no inputs and outputs will be added by other entities, PSBT_GLOBAL_TX_MODIFIABLE may be omitted.
===Constructor===