You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: bip-0174.mediawiki
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,8 +106,10 @@ The format of each key-value map is as follows:
106
106
| Must be <tt>0x00</tt>.
107
107
|}
108
108
109
-
The first byte of each key specifies the type of the key-value pair. There are global types,
110
-
per-input types, and per-output types.
109
+
At the beginning of each key is a compact size unsigned integer representing the type.
110
+
This compact size unsigned integer must be minimally encoded, i.e. if the value can be represented using one byte, it must be represented as one byte.
111
+
For convenience, this BIP will specify types using their full serialization, so a multi-byte type will have it's full prefix and zero padding as necessary.
112
+
There are global types, per-input types, and per-output types.
111
113
112
114
The currently defined global types are as follows:
113
115
@@ -436,8 +438,6 @@ The Partially Signed Transaction format can be extended in the future by adding
436
438
new types for key-value pairs. Backwards compatibilty will still be maintained as those new
437
439
types will be ignored and passed-through by signers which do not know about them.
438
440
439
-
If one byte type fields were to ever run out, new extensions can still be added by defining multi-byte types where the first byte signals that the next byte indicates the type and so on.
440
-
441
441
===Version Numbers===
442
442
443
443
The Version number field exists only as a safeguard in the event that a backwards incompatible change is introduced to PSBT.
0 commit comments