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
117
118
119
120
121
122
123
124
125
126
127
128
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1VtxdK-0003Yy-0u
for bitcoin-development@lists.sourceforge.net;
Fri, 20 Dec 2013 10:48:42 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.148.107 as permitted sender)
client-ip=62.13.148.107; envelope-from=pete@petertodd.org;
helo=outmail148107.authsmtp.com;
Received: from outmail148107.authsmtp.com ([62.13.148.107])
by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1VtxdI-0001EL-1V for bitcoin-development@lists.sourceforge.net;
Fri, 20 Dec 2013 10:48:41 +0000
Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])
by punt18.authsmtp.com (8.14.2/8.14.2/) with ESMTP id rBKAmXpq032994;
Fri, 20 Dec 2013 10:48:33 GMT
Received: from savin (76-10-178-109.dsl.teksavvy.com [76.10.178.109])
(authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id rBKAmRoe050557
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Fri, 20 Dec 2013 10:48:29 GMT
Date: Fri, 20 Dec 2013 05:48:26 -0500
From: Peter Todd <pete@petertodd.org>
To: Mark Friedenbach <mark@monetize.io>
Message-ID: <20131220104826.GC23836@savin>
References: <52B3A1C8.5000005@monetize.io>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="yLVHuoLXiP9kZBkt"
Content-Disposition: inline
In-Reply-To: <52B3A1C8.5000005@monetize.io>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 43967ccb-6964-11e3-b802-002590a15da7
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aAdMdAIUHFAXAgsB AmUbWlReVFV7WmM7 bAxPbAVDY01GQQRq
WVdMSlVNFUsqc2dw W3xBBxl3dwBDfzB3 bU5mEHRYVUJ9JhUv
X0hdE2kbZGY1a31N WEBaagNUcgZDfk5E bwQuUz1vNG8XDQg5
AwQ0PjZ0MThBJSBS WgQAK04nCWwqJnYk XRcaGi4mGR9Nbjgv
LxEgNl8XFVocPg0q K1YvWEJQLwUfBxY2
X-Authentic-SMTP: 61633532353630.1023:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 76.10.178.109/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Score: -1.5 (-)
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 SPF_PASS SPF: sender matches SPF record
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: petertodd.org]
X-Headers-End: 1VtxdI-0001EL-1V
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP proposal: Authenticated prefix trees
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: Fri, 20 Dec 2013 10:48:42 -0000
--yLVHuoLXiP9kZBkt
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Dec 19, 2013 at 05:47:52PM -0800, Mark Friedenbach wrote:
> This BIP describes the authenticated prefix tree and its many
> variations in terms of its serialized representation. Additional BIPs
> describe the application of authenticated prefix trees to such
> applications as committed indices, document time-stamping, and merged
> mining.
Could you expand more on how prefix trees could be used for
time-stamping and merged mining?
> >>> dict =3D AuthTree()
> >>> dict['Curie'] =3D VARINT(1898)
> >>> dict('Einstein') =3D VARINT(1905)
> >>> dict['Fleming'] =3D VARINT(1928)
> >>> dict['=E4=B8=AD=E6=9C=AC'] =3D VARINT(2009)
I'd be inclined to leave the unicode out of the code examples as many
editors and shells still don't copy-and-paste it nicely. Using it in BIP
documents themselves is fine and often has advantages re: typesetting,
but using it in crypto examples like this just makes it harder to
reproduce the results by hand unnecessarily.
--=20
'peter'[:-1]@petertodd.org
0000000000000002d7a0c56ae2c5b2b3322d5017cfef847455d4d86a6bc12280
--yLVHuoLXiP9kZBkt
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQGrBAEBCACVBQJStCB6XhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDJkN2EwYzU2YWUyYzViMmIzMzIyZDUwMTdjZmVmODQ3NDU1
ZDRkODZhNmJjMTIyODAvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkftZKQf+OKaiL2Q4miPnXoF9DLYh9J1E
wsywernlU0g+GXCJMczZYOjsL3JuKeB4DGhabeoYUdPZC8wpdO6+gK68Lo8mi+X6
5IUUh3RoHztqRyhnUjjWOZBM3MCgaErG5RgzTLdxP2sVZxtkbjhn11PJZT+UUGx5
kFI0yH+wzkh3MwJ9x+ymyhNpiinbBw2dlHihdA8mxeV5oqqLiLjaMaamzQf8UQ8k
WaXt9kuwQRtfHooViEAwX6fEf2klSlb+67uqlPsILnhm4+I+fZbyeHlWM1dIfCbu
9UPXaa/y2q5gcmZxZ0u7K3DgVloqo0pUolhnR6zsoMXVtmXXqcSQnnRYfi4v0Q==
=0MET
-----END PGP SIGNATURE-----
--yLVHuoLXiP9kZBkt--
|