Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 86AAE9D for ; Wed, 14 Oct 2015 18:39:29 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-qg0-f47.google.com (mail-qg0-f47.google.com [209.85.192.47]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C2BC31BE for ; Wed, 14 Oct 2015 18:39:28 +0000 (UTC) Received: by qgx61 with SMTP id 61so50957055qgx.3 for ; Wed, 14 Oct 2015 11:39:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=yPf1Ti8Ag2UWMbFToOMpMozGr0pSYiv5F6kXhKuw9o8=; b=jnav2GGVwi0piZR4MdDJvGfBusz24niAEaNvS++jUgMmh36JSXmiSA31oRafUHUIHk oNUoBH2Emqw4F1p8ldK6QfFHcmOh6i65oN+NskI1DHFJ8SBa2ISZwHaa9VthDBqUUzdS PvXieQHcBIWKIsvJBrFuTXw49yqvCQ8B8cw3LjHU6NYBxWZ21MwKW1FD1ak9CzXeoJ2w ZtYQgBIT2tJKWgvRPtRKv1+ZPRBEWaIgusAR8rYZC74G0yLSgskiqjdq91zmz+XVXqKL t3eea2/SWWaXAbajbFg/nLbci1WhupIme/AwSDwNGrbFU+oo1Nf4eLUg8FT116v2gt93 w5eQ== X-Received: by 10.141.28.2 with SMTP id f2mr6297668qhe.59.1444847968069; Wed, 14 Oct 2015 11:39:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.81.149 with HTTP; Wed, 14 Oct 2015 11:39:08 -0700 (PDT) In-Reply-To: <20151014182055.GC23875@mcelrath.org> References: <20151014182055.GC23875@mcelrath.org> From: =?UTF-8?Q?Emin_G=C3=BCn_Sirer?= Date: Wed, 14 Oct 2015 14:39:08 -0400 Message-ID: To: Bob McElrath Content-Type: multipart/alternative; boundary=001a11423974e431bf052214e111 X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW 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 18:39:29 -0000 --001a11423974e431bf052214e111 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable >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. Good point. If NG is layered on top of Bitcoin, we'd retain all of Bitcoin as is. This would confer all the benefits of Bitcoin's retrospective blocks, as well as add the ability to mint microblocks with low latency in between. And despite the phrase "the leader," the actual leader in NG is a key, not a specific node. That makes it possible to deter DDoS attacks by dynamically migrating where in the network the leader is operating in response to an attack. Finally, DDoS attacks against miners are already possible, but they seem rare, and I suspect it's at least partly because of the success of Matt Corallo's high speed bitcoin relay network. Similar defenses can apply here. - egs On Wed, Oct 14, 2015 at 2:20 PM, Bob McElrath wrote: > 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=C3=BCn Sirer via bitcoin-dev [bitcoin-dev@lists.linuxfoundation.or= g] > 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 tru= st > > 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 compe= te > > 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=C3=BCn 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 > > --001a11423974e431bf052214e111 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
>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 Bit= coin-NG down.

Good point. If NG is layered on top = of Bitcoin, we'd retain all of Bitcoin as is. This would confer all the= benefits of Bitcoin's retrospective blocks, as well as add the ability= to mint microblocks with low latency in between. And despite the phrase &q= uot;the leader," the actual leader in NG is a key, not a specific node= . That makes it possible to deter DDoS attacks by dynamically migrating whe= re in the network the leader is operating in response to an attack. Finally= , DDoS attacks against miners are already possible, but they seem rare, and= I suspect it's at least partly because of the success of Matt Corallo&= #39;s high speed bitcoin relay network. Similar defenses can apply here.

- egs



On Wed, Oct 14, 2015 a= t 2:20 PM, Bob McElrath <bob@mcelrath.org> wrote:
So it seems to me that all I need to do is figure ou= t 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 o= ne knows
where the next one will come from.=C2=A0 The only way to shut the network d= own is to
shut all nodes down.

Emin G=C3=BCn 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. Surpri= singly,
> Bitcoin-NG can simultaneously increase throughput while reducing laten= cy, and
> do so without impacting Bitcoin's open architecture or changing it= s trust
> model. This post illustrates the core technique:
> =C2=A0 =C2=A0 =C2=A0http://hackingdistribut= ed.com/2015/10/14/bitcoin-ng/
> while the whitepaper has all the nitty gritty details:
> =C2=A0 =C2=A0 =C2=A0http://arxiv.org/abs/1510.02037
>
> Fitting NG on top of the current Bitcoin blockchain is future work tha= t 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 comp= ete
> commercially with either technology -- we see NG as being complementar= y 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 an= d
> latencies required of cutting edge fintech applications. Perhaps it ca= n be
> adopted, or perhaps it can provide the spark of inspiration for someon= e else to
> come up with even better solutions.
>
> We would be delighted to hear your feedback.=C2=A0
> - Ittay Eyal and E. G=C3=BCn Sirer.
>
> !DSPAM:561e98cd301391127216946!

> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@l= ists.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."
=C2=A0 =C2=A0 -- H. L. Mencken


--001a11423974e431bf052214e111--