MIME-Version: 1.0
In-Reply-To: <CAFp6fsHBbyVo21DnQKGBVJ7P=8NqOGJ-jv0-MH9WaBD6vauudA@mail.gmail.com>
References: <CAFp6fsHBbyVo21DnQKGBVJ7P=8NqOGJ-jv0-MH9WaBD6vauudA@mail.gmail.com>
Date: Thu, 24 Sep 2015 19:17:50 +0100
Message-ID: <CAE-z3OUKTKh5-SHkiawr4R58Fdg9N6_1PLjW19YsF-K9OOjQow@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a1143dda0ba41da0520823fe2
Subject: Re: [bitcoin-dev] [BIP Proposal] New "sendheaders" p2p message
Precedence: list

--001a1143dda0ba41da0520823fe2
Content-Type: text/plain; charset=UTF-8

On Thu, Sep 24, 2015 at 7:02 PM, Suhas Daftuar via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Hi,
>
> I'm proposing the addition of a new, optional p2p message to help improve
> the way blocks are announced on the network.  The draft BIP is available
> here and pasted below:
> https://gist.github.com/sdaftuar/465bf008f0a4768c0def
>
> The goal of this p2p message is to facilitate nodes being able to
> optionally announce blocks with headers messages rather than with inv's,
> which is particularly beneficial since the introduction of headers-first
> download in Bitcoin Core 0.10.  In particular, this allows for more
> efficient propagation of reorgs as it would eliminate a round trip in
> network communication.
>

Is there actually a requirement for the new message?  New nodes could just
unilaterally switch to sending headers and current nodes would be
compatible.

It looks like the only DOS misbehaving penalty is if the header is invalid
or if the headers don't form a chain.

--001a1143dda0ba41da0520823fe2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Sep 24, 2015 at 7:02 PM, Suhas Daftuar via bitcoin-dev <span dir=3D"ltr=
">&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_b=
lank">bitcoin-dev@lists.linuxfoundation.org</a>&gt;</span> wrote:<br><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex"><div dir=3D"ltr">Hi,<div><br></div><div>I&#39;m pr=
oposing the addition of a new, optional p2p message to help improve the way=
 blocks are announced on the network.=C2=A0 The draft BIP is available here=
 and pasted below:</div><div><div><a href=3D"https://gist.github.com/sdaftu=
ar/465bf008f0a4768c0def" target=3D"_blank">https://gist.github.com/sdaftuar=
/465bf008f0a4768c0def</a></div></div><div><br></div><div>The goal of this p=
2p message is to facilitate nodes being able to optionally announce blocks =
with headers messages rather than with inv&#39;s, which is particularly ben=
eficial since the introduction of headers-first download in Bitcoin Core 0.=
10.=C2=A0 In particular, this allows for more efficient propagation of reor=
gs as it would eliminate a round trip in network communication.</div></div>=
</blockquote><div><br></div><div>Is there actually a requirement for the ne=
w message?=C2=A0 New nodes could just unilaterally switch to sending header=
s and current nodes would be compatible.<br><br></div><div>It looks like th=
e only DOS misbehaving penalty is if the header is invalid or if the header=
s don&#39;t form a chain.<br></div></div></div></div>

--001a1143dda0ba41da0520823fe2--