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 ) 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 ; 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: References: Date: Wed, 4 Mar 2015 07:28:53 -0800 X-Google-Sender-Auth: coD0UEH0vHvK3Rl3k49vAn7yYL4 Message-ID: From: Mike Hearn To: Andrew Miller 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 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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
Nice, Andrew.

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.

On Mon, Mar 2, 2015 a= t 8:48 AM, Andrew Miller <amiller@cs.umd.edu> wrote:
We (Joseph Bonneau, myself Arvind Narayanan, Je= remy Clark, Ed Felten,
Josh Kroll -- from Stanford, Maryland, Concordia, Princeton) have
written a =E2=80=9Csystemization=E2=80=9D paper about Bitcoin-related resea= rch. 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, sponso= red
by Intel and developed in partnership with Slashdot Media, is your hub for = all
things parallel software development, from weekly thought leadership blogs = 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-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--047d7b66fa5fe40cf60510781be4--