1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <kristovatlas.lists@gmail.com>) id 1Z17XK-0005KP-Gq
for bitcoin-development@lists.sourceforge.net;
Sat, 06 Jun 2015 06:24:54 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.43 as permitted sender)
client-ip=209.85.215.43;
envelope-from=kristovatlas.lists@gmail.com;
helo=mail-la0-f43.google.com;
Received: from mail-la0-f43.google.com ([209.85.215.43])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z17XJ-0005Kr-LF
for bitcoin-development@lists.sourceforge.net;
Sat, 06 Jun 2015 06:24:54 +0000
Received: by labpy14 with SMTP id py14so67077369lab.0
for <bitcoin-development@lists.sourceforge.net>;
Fri, 05 Jun 2015 23:24:47 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.112.54.225 with SMTP id m1mr6849381lbp.34.1433571887271;
Fri, 05 Jun 2015 23:24:47 -0700 (PDT)
Received: by 10.152.163.98 with HTTP; Fri, 5 Jun 2015 23:24:47 -0700 (PDT)
In-Reply-To: <44BE16F9-AB24-4A8E-BC7F-03A6C590FCE7@gmail.com>
References: <CAGH37SK0k1YUvadetyHcBGjzW+OHNFRmRwqsUDeHBGejUacigQ@mail.gmail.com>
<44BE16F9-AB24-4A8E-BC7F-03A6C590FCE7@gmail.com>
Date: Sat, 6 Jun 2015 02:24:47 -0400
Message-ID: <CAGH37SL3TA7BXd3Y+4F1Fd5N3ZW+LRLvkfppPsPn61ZVbZJOnQ@mail.gmail.com>
From: Kristov Atlas <kristovatlas.lists@gmail.com>
To: Stephen <stephencalebmorse@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c3ecfe19d3340517d377ae
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(kristovatlas.lists[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Z17XJ-0005Kr-LF
Cc: Bitcoin development mailing list
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Lexicographical Indexing of Transaction
Inputs and Outputs
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sat, 06 Jun 2015 06:24:54 -0000
--001a11c3ecfe19d3340517d377ae
Content-Type: text/plain; charset=UTF-8
Hey Stephen,
Thanks for your feedback
On Fri, Jun 5, 2015 at 11:20 PM, Stephen <stephencalebmorse@gmail.com>
wrote:
> - I think your explanation of sorting could be significantly shortened
> and clarified by simply saying that the TXIDs of inputs should be compared
> as uint256 integers.
>
I considered defining the comparison of txids in terms of integers;
however, I am concerned that this definition may be ambiguous when applied
to a variety of languages and platforms without a similar amount of
explanation as currently exists. For example, if a web wallet uses an API
to receive transaction information, this is traditionally expressed in
terms tx id strings rather than 256-bit integers. My intent is that wallets
can implement the algorithm however they wish, but should ensure that their
output is compliant with the BIP definition. IMHO the algorithm stated in
the BIP should target test cases rather than implementation, and should
leave as little room for ambiguity as possible.
--001a11c3ecfe19d3340517d377ae
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Hey Stephen,<br><br></div>Thanks for your feedback<di=
v class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Jun 5, 2015 =
at 11:20 PM, Stephen <span dir=3D"ltr"><<a href=3D"mailto:stephencalebmo=
rse@gmail.com" target=3D"_blank">stephencalebmorse@gmail.com</a>></span>=
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto"><div>=C2=A0- I =
think your explanation of sorting could be significantly shortened and clar=
ified by simply saying that the TXIDs of inputs should be compared as uint2=
56 integers.=C2=A0</div></div></blockquote><div><br></div><div>I considered=
defining the comparison of txids in terms of integers; however, I am conce=
rned that this definition may be ambiguous when applied to a variety of lan=
guages and platforms without a similar amount of explanation as currently e=
xists. For example, if a web wallet uses an API to receive transaction info=
rmation, this is traditionally expressed in terms tx id strings rather than=
256-bit integers. My intent is that wallets can implement the algorithm ho=
wever they wish, but should ensure that their output is compliant with the =
BIP definition. IMHO the algorithm stated in the BIP should target test cas=
es rather than implementation, and should leave as little room for ambiguit=
y as possible. <br></div></div></div></div>
--001a11c3ecfe19d3340517d377ae--
|
