From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 8B1A7273 for ; Wed, 14 Oct 2015 20:52:42 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mcelrath.org (moya.mcelrath.org [50.31.3.130]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E727A110 for ; Wed, 14 Oct 2015 20:52:41 +0000 (UTC) Received: from mcelrath.org (localhost [127.0.0.1]) by mcelrath.org (8.14.3/8.14.3/Debian-9.4) with ESMTP id t9EKqZ9Q001528 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 14 Oct 2015 20:52:35 GMT Received: (from mcelrath@localhost) by mcelrath.org (8.14.3/8.14.3/Submit) id t9EKqZSx001527; Wed, 14 Oct 2015 20:52:35 GMT X-Authentication-Warning: mcelrath.org: mcelrath set sender to bob_bitcoin@mcelrath.org using -f Date: Wed, 14 Oct 2015 20:52:35 +0000 From: Bob McElrath To: Emin =?iso-8859-1?B?R/xu?= Sirer Message-ID: <20151014205235.GD23875@mcelrath.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: bitcoin-dev@lists.linuxfoundation.org, Ittay Eyal Subject: Re: [bitcoin-dev] Bitcoin-NG whitepaper. X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2015 20:52:42 -0000 So it seems to me that all I need to do is figure out who the current leader is, and DDoS him off the network to shut Bitcoin-NG down. This is a significant advantage to bitcoin's ex-post-facto blocks: no one knows where the next one will come from. The only way to shut the network down is to shut all nodes down. Emin Gün Sirer via bitcoin-dev [bitcoin-dev@lists.linuxfoundation.org] wrote: > Hi everyone, > > We just released the whitepaper describing Bitcoin-NG, a new technique for > addressing some of the scalability challenges faced by Bitcoin. Surprisingly, > Bitcoin-NG can simultaneously increase throughput while reducing latency, and > do so without impacting Bitcoin's open architecture or changing its trust > model. This post illustrates the core technique: >      http://hackingdistributed.com/2015/10/14/bitcoin-ng/ > while the whitepaper has all the nitty gritty details: >      http://arxiv.org/abs/1510.02037 > > Fitting NG on top of the current Bitcoin blockchain is future work that we > think is quite possible. NG is compatible with both Bitcoin as is, as well as > Blockstream-like sidechains, and we currently are not planning to compete > commercially with either technology -- we see NG as being complementary to both > efforts. This is pure science, published and shared with the community to > advance the state of blockchains and to help them reach throughputs and > latencies required of cutting edge fintech applications. Perhaps it can be > adopted, or perhaps it can provide the spark of inspiration for someone else to > come up with even better solutions. > > We would be delighted to hear your feedback.  > - Ittay Eyal and E. Gün Sirer. > > !DSPAM:561e98cd301391127216946! > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > > > !DSPAM:561e98cd301391127216946! -- Cheers, Bob McElrath "For every complex problem, there is a solution that is simple, neat, and wrong." -- H. L. Mencken