From b6b19894c211e2ef10edac20c86e509ac06e8f65 Mon Sep 17 00:00:00 2001 From: Dustin Dettmer Date: Sun, 10 Feb 2019 15:42:35 -0800 Subject: [PATCH] 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. --- bip-0174.mediawiki | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/bip-0174.mediawiki b/bip-0174.mediawiki index 31a593dd..a3098a47 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 0x00 byte '''Why +Each map consists of a sequence of key-value records, terminated by a 0x00 byte '''Why is the separator here 0x00 instead of 0xff?''' 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.. The format +be used as a separator and allow for easier unserializer implementation.. +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: <..> indicates that the data is prefixed by a compact size unsigned integer representing