From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YSTWF-0002gw-J7 for bitcoin-development@lists.sourceforge.net; Mon, 02 Mar 2015 16:48:35 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of cs.umd.edu designates 128.8.127.43 as permitted sender) client-ip=128.8.127.43; envelope-from=amiller@cs.umd.edu; helo=sausage.cs.umd.edu; Received: from sausage.cs.umd.edu ([128.8.127.43]) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1YSTWD-0000xs-4H for bitcoin-development@lists.sourceforge.net; Mon, 02 Mar 2015 16:48:35 +0000 Received: from mail-lb0-f170.google.com (mail-lb0-f170.google.com [209.85.217.170]) (Authenticated sender: amiller) by sausage.cs.umd.edu (Postfix) with ESMTPSA id 31D056C0E0B for ; Mon, 2 Mar 2015 11:48:25 -0500 (EST) Received: by lbvn10 with SMTP id n10so31313229lbv.6 for ; Mon, 02 Mar 2015 08:48:24 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.152.6.66 with SMTP id y2mr25090742lay.25.1425314904127; Mon, 02 Mar 2015 08:48:24 -0800 (PST) Received: by 10.114.184.103 with HTTP; Mon, 2 Mar 2015 08:48:24 -0800 (PST) Date: Mon, 2 Mar 2015 11:48:24 -0500 Message-ID: From: Andrew Miller To: Bitcoin-development@lists.sourceforge.net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.3.9 (sausage.cs.umd.edu [0.0.0.0]); Mon, 02 Mar 2015 11:48:25 -0500 (EST) X-CSD-MailScanner-ID: 31D056C0E0B.ADD63 X-CSD-MailScanner: Found to be clean X-CSD-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-49.99, required 5, autolearn=not spam, ALL_TRUSTED -50.00, T_DKIM_INVALID 0.01) X-CSD-MailScanner-From: amiller@cs.umd.edu X-CSD-MailScanner-Watermark: 1425919705.93013@3ZpMzQMS+aU6bcvUoP0Qbg X-Spam-Status: No X-Spam-Score: -1.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 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_PASS SPF: sender matches SPF record -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: 1YSTWD-0000xs-4H Subject: [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: Mon, 02 Mar 2015 16:48:35 -0000 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 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.