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
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1YTBEL-0005EQ-Fy
for Bitcoin-development@lists.sourceforge.net;
Wed, 04 Mar 2015 15:29:01 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.174 as permitted sender)
client-ip=74.125.82.174; envelope-from=mh.in.england@gmail.com;
helo=mail-we0-f174.google.com;
Received: from mail-we0-f174.google.com ([74.125.82.174])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YTBEJ-0000v0-MD
for Bitcoin-development@lists.sourceforge.net;
Wed, 04 Mar 2015 15:29:01 +0000
Received: by wesp10 with SMTP id p10so44889636wes.12
for <Bitcoin-development@lists.sourceforge.net>;
Wed, 04 Mar 2015 07:28:53 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.61.51 with SMTP id m19mr9156274wjr.39.1425482933601;
Wed, 04 Mar 2015 07:28:53 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.194.188.11 with HTTP; Wed, 4 Mar 2015 07:28:53 -0800 (PST)
In-Reply-To: <CAF7tpEyHyg7cB8DQiwb-gGg5v5Hn1Kurw2GaVtid=LyJrB1XQA@mail.gmail.com>
References: <CAF7tpEyHyg7cB8DQiwb-gGg5v5Hn1Kurw2GaVtid=LyJrB1XQA@mail.gmail.com>
Date: Wed, 4 Mar 2015 07:28:53 -0800
X-Google-Sender-Auth: coD0UEH0vHvK3Rl3k49vAn7yYL4
Message-ID: <CANEZrP33SSVVj_+bLXiK_HZLDGr8t7PJLs5f2QPrDRB_1mn__A@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Andrew Miller <amiller@cs.umd.edu>
Content-Type: multipart/alternative; boundary=047d7b66fa5fe40cf60510781be4
X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1YTBEJ-0000v0-MD
Cc: Bitcoin Dev <Bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] New paper: Research Perspectives and
Challenges for Bitcoin and Cryptocurrencies
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: Wed, 04 Mar 2015 15:29:01 -0000
--047d7b66fa5fe40cf60510781be4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Nice, Andrew.
Just one minor point. SPV clients do not need to maintain an ever growing
list of PoW solutions. BitcoinJ uses a ring buffer with 5000 headers and
thus has O(1) disk usage. Re-orgs past the event horizon cannot be
processed but are assumed to be sufficiently rare that manual intervention
would be acceptable.
On Mon, Mar 2, 2015 at 8:48 AM, Andrew Miller <amiller@cs.umd.edu> wrote:
> We (Joseph Bonneau, myself Arvind Narayanan, Jeremy Clark, Ed Felten,
> Josh Kroll -- from Stanford, Maryland, Concordia, Princeton) have
> written a =E2=80=9Csystemization=E2=80=9D paper about Bitcoin-related res=
earch. It=E2=80=99s
> going to appear in the Oakland security conference later this year
> (IEEE Security and Privacy) but we wanted to announce a draft to this
> community ahead of time.
>
> http://www.jbonneau.com/doc/BMCNKF15-IEEESP-bitcoin.pdf
>
> One of the main goals of our work is to build a bridge between the
> computer science research community and the cryptocurrency community.
> Many of the most interesting ideas and proposals for Bitcoin come from
> this mailing list and forums/wikis/irc channels, where many academic
> researchers simply don=E2=80=99t know to look! In fact, we started out by
> scraping all the interesting posts/articles we could find and trying
> to figure out how we could organize them. We hope our paper helps some
> of the best ideas and research questions from the Bitcoin community
> bubble up and inspires researchers to build on them.
>
> We didn=E2=80=99t limit our scope to Bitcoin, but we also decided not to
> provide a complete survey of altcoins and other next-generation
> cryptocurrency designs. Instead, we tried to explain all the
> dimensions along which these designs differ from Bitcoin.
>
> This effort has roughly been in progress over two years, though it
> stopped and restarted several times along the way.
>
> If anyone has comments or suggestions, we still have a week before the
> final version is due, and regardless we plan to continue updating our
> online version for the forseeable future.
>
>
> -------------------------------------------------------------------------=
-----
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub fo=
r
> all
> things parallel software development, from weekly thought leadership blog=
s
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--047d7b66fa5fe40cf60510781be4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Nice, Andrew.<div><br></div><div>Just one minor point. SPV=
clients do not need to maintain an ever growing list of PoW solutions. Bit=
coinJ uses a ring buffer with 5000 headers and thus has O(1) disk usage. Re=
-orgs past the event horizon cannot be processed but are assumed to be suff=
iciently rare that manual intervention would be acceptable.</div></div><div=
class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Mar 2, 2015 a=
t 8:48 AM, Andrew Miller <span dir=3D"ltr"><<a href=3D"mailto:amiller@cs=
.umd.edu" target=3D"_blank">amiller@cs.umd.edu</a>></span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">We (Joseph Bonneau, myself Arvind Narayanan, Je=
remy Clark, Ed Felten,<br>
Josh Kroll -- from Stanford, Maryland, Concordia, Princeton) have<br>
written a =E2=80=9Csystemization=E2=80=9D paper about Bitcoin-related resea=
rch. It=E2=80=99s<br>
going to appear in the Oakland security conference later this year<br>
(IEEE Security and Privacy) but we wanted to announce a draft to this<br>
community ahead of time.<br>
<br>
<a href=3D"http://www.jbonneau.com/doc/BMCNKF15-IEEESP-bitcoin.pdf" target=
=3D"_blank">http://www.jbonneau.com/doc/BMCNKF15-IEEESP-bitcoin.pdf</a><br>
<br>
One of the main goals of our work is to build a bridge between the<br>
computer science research community and the cryptocurrency community.<br>
Many of the most interesting ideas and proposals for Bitcoin come from<br>
this mailing list and forums/wikis/irc channels, where many academic<br>
researchers simply don=E2=80=99t know to look! In fact, we started out by<b=
r>
scraping all the interesting posts/articles we could find and trying<br>
to figure out how we could organize them. We hope our paper helps some<br>
of the best ideas and research questions from the Bitcoin community<br>
bubble up and inspires researchers to build on them.<br>
<br>
We didn=E2=80=99t limit our scope to Bitcoin, but we also decided not to<br=
>
provide a complete survey of altcoins and other next-generation<br>
cryptocurrency designs. Instead, we tried to explain all the<br>
dimensions along which these designs differ from Bitcoin.<br>
<br>
This effort has roughly been in progress over two years, though it<br>
stopped and restarted several times along the way.<br>
<br>
If anyone has comments or suggestions, we still have a week before the<br>
final version is due, and regardless we plan to continue updating our<br>
online version for the forseeable future.<br>
<br>
---------------------------------------------------------------------------=
---<br>
Dive into the World of Parallel Programming The Go Parallel Website, sponso=
red<br>
by Intel and developed in partnership with Slashdot Media, is your hub for =
all<br>
things parallel software development, from weekly thought leadership blogs =
to<br>
news, videos, case studies, tutorials and more. Take a look and join the<br=
>
conversation now. <a href=3D"http://goparallel.sourceforge.net/" target=3D"=
_blank">http://goparallel.sourceforge.net/</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div>
--047d7b66fa5fe40cf60510781be4--
|
