diff options
| author | Dustin Dettmer <dustinpaystaxes@gmail.com> | 2019-02-10 15:42:35 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-02-10 15:42:35 -0800 |
| commit | b6b19894c211e2ef10edac20c86e509ac06e8f65 (patch) | |
| tree | 0d10b05f2351b7f9fa0f392ccd819ce0cb1164a1 /bip-0174.mediawiki | |
| parent | 954df0d10728dd704fa4b378255ae23e6a5952a0 (diff) | |
| download | bips-b6b19894c211e2ef10edac20c86e509ac06e8f65.tar.xz | |
Flipping the sentence order here for simplicity.
Being new to the spec, I had to reread this multiple times to understand it. Ordering the setences according to scope seems to make it easier to grock.
Diffstat (limited to 'bip-0174.mediawiki')
| -rw-r--r-- | bip-0174.mediawiki | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/bip-0174.mediawiki b/bip-0174.mediawiki index 31a593d..a3098a4 100644 --- a/bip-0174.mediawiki +++ b/bip-0174.mediawiki @@ -43,12 +43,12 @@ risk of being defrauded. ==Specification== The Partially Signed Bitcoin Transaction (PSBT) format consists of key-value maps. -Each key-value pair must have a unique key within its scope; duplicates are not allowed. -Each map consists of a sequence of records, terminated by a <tt>0x00</tt> byte <ref>'''Why +Each map consists of a sequence of key-value records, terminated by a <tt>0x00</tt> byte <ref>'''Why is the separator here <tt>0x00</tt> instead of <tt>0xff</tt>?''' The separator here is used to distinguish between each chunk of data. A separator of 0x00 would mean that the unserializer can read it as a key length of 0, which would never occur with actual keys. It can thus -be used as a separator and allow for easier unserializer implementation.</ref>. The format +be used as a separator and allow for easier unserializer implementation.</ref>. +Each key-value pair must have a unique key within its scope; duplicates are not allowed. The format of a record is as follows: Note: <tt><..></tt> indicates that the data is prefixed by a compact size unsigned integer representing |