Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.160.172 as permitted sender)
	client-ip=209.85.160.172; envelope-from=gavinandresen@gmail.com;
	helo=mail-yk0-f172.google.com; 
MIME-Version: 1.0
In-Reply-To: <CAJHLa0NZRF+1QjSwtwjaTE07NWJ_U-O-DE24=P5eSAutMqTupg@mail.gmail.com>
References: <CA+iPb=EaX=bvOjNtZ+LnYTMRLQQ9nFcrefAkBdv8eActoX_b8A@mail.gmail.com>
	<CABsx9T0ag_o_mu=5Q7Ju7s2hO3jz-o5g9FihE9h4B6+ednd2Pg@mail.gmail.com>
	<CAJHLa0NZRF+1QjSwtwjaTE07NWJ_U-O-DE24=P5eSAutMqTupg@mail.gmail.com>
Date: Fri, 18 Jul 2014 10:53:01 -0400
Message-ID: <CABsx9T2BDBNqvinVNk3FmBRWU7R8jf6Vm6NaH74te0FRCh1O-w@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=089e0160a63efa739604fe78e9aa
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Squashing redundant tx data in blocks on
 the wire
Precedence: list

--089e0160a63efa739604fe78e9aa
Content-Type: text/plain; charset=ISO-8859-1

Two more half-baked thoughts:

We should be able to assume that the majority of transaction data (except
for coinbase) has already been propagated. As Jeff said, incentivizing
nodes to propagate transactions is a very good thing (the signature cache
already gives a small incentive to miners to propagate and not 'hoard'
transactions).

So the only information that theoretically needs to be propagated is which
transactions a miner is including in their block, and in what order they
are included.

But if there was some agreed-upon canonical ordering, then it should
theoretically be possible to take shortcuts in the "what order".

You'd start with setof(transactions I think everybody knows about)
Select some subset, based on miner's policy
Sort that subset with the canonical ordering algorithm
Very efficiently broadcast, taking all sorts of shortcuts assuming most of
your peers already know the set you started with and expect the same
canonical ordering (see gmaxwell's thoughts on block encoding).

Second half-baked thought:
I wonder if broadcasting your transaction selection policy ("11KB of free
transactions, sorted by priority, then 111K of fee-paying transactions,
sorted by fee") might make it possible to save even more bandwidth by
letting your peers create a very good approximation of your block with just
that information....

-- 
--
Gavin Andresen

--089e0160a63efa739604fe78e9aa
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Two more half-baked thoughts:<div><br></div><div>We should=
 be able to assume that the majority of transaction data (except for coinba=
se) has already been propagated. As Jeff said, incentivizing nodes to propa=
gate transactions is a very good thing (the signature cache already gives a=
 small incentive to miners to propagate and not &#39;hoard&#39; transaction=
s).</div>
<div><br></div><div>So the only information that theoretically needs to be =
propagated is which transactions a miner is including in their block, and i=
n what order they are included.</div><div><br></div><div>But if there was s=
ome agreed-upon canonical ordering, then it should theoretically be possibl=
e to take shortcuts in the &quot;what order&quot;.</div>
<div><br></div><div>You&#39;d start with setof(transactions I think everybo=
dy knows about)</div><div>Select some subset, based on miner&#39;s policy</=
div><div>Sort that subset with the canonical ordering algorithm</div><div>
Very efficiently broadcast, taking all sorts of shortcuts assuming most of =
your peers already know the set you started with and expect the same canoni=
cal ordering (see gmaxwell&#39;s thoughts on block encoding).</div><div>
<br></div><div>Second half-baked thought:</div><div>I wonder if broadcastin=
g your transaction selection policy (&quot;11KB of free transactions, sorte=
d by priority, then 111K of fee-paying transactions, sorted by fee&quot;) m=
ight make it possible to save even more bandwidth by letting your peers cre=
ate a very good approximation of your block with just that information....<=
/div>
<div class=3D"gmail_extra"><div class=3D"gmail_quote"><br></div>-- <br>--<b=
r>Gavin Andresen<br>
</div><div class=3D"gmail_extra"><br></div></div>

--089e0160a63efa739604fe78e9aa--