[Bitcoin-development] Squashing redundant tx data in blocks on the wire

Jeff Garzik jgarzik at bitpay.com
Fri Jul 18 13:53:35 UTC 2014

On Thu, Jul 17, 2014 at 6:46 PM, Gavin Andresen <gavinandresen at gmail.com> wrote:
> I'd encourage you to code up a prototype first (or at the same time), in
> whatever programming language / networking library you're most familiar
> with.


> Maybe not even using the existing p2p protocol; there could be a mining-only
> very-fast-block-propagation network separate from the existing p2p network.
> Combining your optimizations with "broadcast as many near-miss blocks as
> bandwidth will allow" on a mining backbone network should allow insanely
> fast propagation of most newly solved blocks.

Yes, I would encourage thinking along these lines.  That was the
motivation of the UDP P2P protocol extension I wrote:

The intention was to experiment with sending block header + tx list +
coinbase, via UDP best effort broadcast.


If your neighbors receiving this message already have the TXs in the
TX list, then the block is complete, and may be relayed further.

If your neighbors do not have all TXs in the block, they must fetch
them at additional time/latency cost.

Thus, you have an incentive to relay blocks containing TXs already
distributed out into network mempools and cached in the signature

We want to capture that incentive in whatever protocol is eventually
used.  Miners have a TX fee incentive to include many transactions.
In theory, they want to include as many TX as possible.  It will help
us scale quite a bit to solve this problem.

More information about the bitcoin-dev mailing list