summaryrefslogtreecommitdiff
path: root/bip-0174.mediawiki
diff options
context:
space:
mode:
authorSjors Provoost <sjors@sprovoost.nl>2022-01-12 16:37:01 +0100
committerSjors Provoost <sjors@sprovoost.nl>2022-01-12 16:39:21 +0100
commit6366f8ebcbab1bc5e59325bf8a00ed96065bd671 (patch)
tree9f1af9229ee60d8d1a911cbb3a2de8fc92ac12e6 /bip-0174.mediawiki
parentdc034af961132a3593fb2d4f81ddb06c67c2b6d2 (diff)
downloadbips-6366f8ebcbab1bc5e59325bf8a00ed96065bd671.tar.xz
bip174: document PSBT 0 handling of type > 0xFD
Diffstat (limited to 'bip-0174.mediawiki')
-rw-r--r--bip-0174.mediawiki3
1 files changed, 3 insertions, 0 deletions
diff --git a/bip-0174.mediawiki b/bip-0174.mediawiki
index 8ef525c..874af14 100644
--- a/bip-0174.mediawiki
+++ b/bip-0174.mediawiki
@@ -819,6 +819,9 @@ If an updater is updating a PSBT and needs to add a field that is only available
New fields should first be proposed on the bitcoin-dev mailing list.
If a field requires significant description as to its usage, it should be accompanied by a separate BIP.
The field must be added to the field listing tables in the Specification section.
+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===