MIME-Version: 1.0
In-Reply-To: <CAAS2fgRj+fE+znXZzFsXXBivKSxnJ2Lheo_g9us4FXN_yCLhgw@mail.gmail.com>
References: <CABsx9T2+dG0AE+MgKRAU97KhkHTU1MuxXuwHKv3BgpJswZ5vVg@mail.gmail.com>
	<CABaSBaxcDRzw0X7-fAfxPJyLcWxTHigpHuAPb4aNQ5zk5NoDCQ@mail.gmail.com>
	<CAAS2fgTr-OuL3T6mXX-4xFC_LHnAiogTTcPMbcjsM7WtRisQEQ@mail.gmail.com>
	<CABsx9T3NFRO5nw3z=jrs0Hu3caVNkkTTTb1ibqR7LMWsoou9RQ@mail.gmail.com>
	<CAAS2fgRj+fE+znXZzFsXXBivKSxnJ2Lheo_g9us4FXN_yCLhgw@mail.gmail.com>
Date: Sun, 27 Sep 2015 10:42:24 +0100
Message-ID: <CAE-z3OU50cZBR27QrQsRT5Gtb0AVkE6K33XR0GebsyNWNrbf+w@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a11459a40f2eb9b0520b7657a
Subject: Re: [bitcoin-dev] Weak block thoughts...
Precedence: list

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

On Sun, Sep 27, 2015 at 2:39 AM, Gregory Maxwell via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Unless the weak block transaction list can be a superset of the block
> transaction list size proportional propagation costs are not totally
> eliminated.
>

The POW threshold could be dynamic.  The first weak-block that builds on a
new block could be forwarded with a smaller target.

This reduces  the window size until at least one weak block is propagated.

The change in threshold could be time based (for the first 30 seconds or
so).  This would cause a surge of traffic when a new block once a new block
has propagated, so perhaps not so good an idea.


> As even if the weak block criteria is MUCH lower than the block
> criteria (which would become problematic in its own right at some
> point) the network will sometimes find blocks when there hasn't been
> any weak block priming at all (e.g. all prior priming has made it into
> blocks already).
>

If there is a transaction backlog, then miners could forward merkle
branches with transactions in the memory pool with a commitment in the
coinbase.

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Sun, Sep 27, 2015 at 2:39 AM, Gregory Maxwell via bitcoin-dev <span =
dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" ta=
rget=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><span class=3D"">
</span>Unless the weak block transaction list can be a superset of the bloc=
k<br>
transaction list size proportional propagation costs are not totally<br>
eliminated.<br></blockquote><div><br></div><div>The POW threshold could be =
dynamic.=C2=A0 The first weak-block that builds on a new block could be for=
warded with a smaller target.<br><br></div><div>This reduces=C2=A0 the wind=
ow size until at least one weak block is propagated.=C2=A0 <br><br></div><d=
iv>The change in threshold could be time based (for the first 30 seconds or=
 so).=C2=A0 This would cause a surge of traffic when a new block once a new=
 block has propagated, so perhaps not so good an idea.<br></div><div><br></=
div><div></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
<br>
As even if the weak block criteria is MUCH lower than the block<br>
criteria (which would become problematic in its own right at some<br>
point) the network will sometimes find blocks when there hasn&#39;t been<br=
>
any weak block priming at all (e.g. all prior priming has made it into<br>
blocks already).<br></blockquote><div><br></div><div>If there is a transact=
ion backlog, then miners could forward merkle branches with transactions in=
 the memory pool with a commitment in the coinbase.<br></div></div></div></=
div>

--001a11459a40f2eb9b0520b7657a--