Pulls in most of the formatting changes from #953. Also explicitly specifies the parts for PSBT version 0 as well as sections for the process of adding new fields and PSBT versions. Lastly marks BIP 174 as final.
Although I am marking it as final, this is only really for the general format. New fields can be added, and those fields should be added to the field listing tables in BIP 174.
"Variable length string identifier" is not defined anywhere, and the suggestion
to use "0x00" is also deeply unclear. I assumed it meant a nul-terminated
string!
Be explicit: you mean it must be a compact siz1\e unsigned int length, followed
by that many identifier bytes, followed by a compact size unsigned int subtype,
followed by optional keydata.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Argh, missed that this violates the length limit. Reverted that part.
Please don’t modify CI to bypass validity checks.
582@@ -509,6 +583,18 @@ Updaters and combiners that need to add a version number to a PSBT should use th
583 For example, if a combiner sees two PSBTs for the same transaction, one with version 0, and the other with version 1, then it should combine them and produce a PSBT with version 1.
584 If an updater is updating a PSBT and needs to add a field that is only available in version 1, then it should set the PSBT version number to 1 unless a version higher than that is already specified.
585
586+===Procedure For New Fields===
587+
588+New fields should first be proposed on the bitcoin-dev mailing list.
589+If a field requires significatn description as to its usage, it should be accompanied by a separate BIP.
