From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1X7v4k-0004Xt-Bu for bitcoin-development@lists.sourceforge.net; Thu, 17 Jul 2014 23:26:58 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.51 as permitted sender) client-ip=209.85.219.51; envelope-from=keziahw@gmail.com; helo=mail-oa0-f51.google.com; Received: from mail-oa0-f51.google.com ([209.85.219.51]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1X7v4i-00037p-Tu for bitcoin-development@lists.sourceforge.net; Thu, 17 Jul 2014 23:26:58 +0000 Received: by mail-oa0-f51.google.com with SMTP id o6so1877275oag.24 for ; Thu, 17 Jul 2014 16:26:51 -0700 (PDT) X-Received: by 10.60.65.170 with SMTP id y10mr624565oes.45.1405639611361; Thu, 17 Jul 2014 16:26:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.98.11 with HTTP; Thu, 17 Jul 2014 16:26:31 -0700 (PDT) In-Reply-To: References: From: Kaz Wesley Date: Thu, 17 Jul 2014 16:26:31 -0700 Message-ID: To: Gavin Andresen Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (keziahw[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1X7v4i-00037p-Tu Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Squashing redundant tx data in blocks on the wire X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2014 23:26:58 -0000 I'm moving this design document to a gist so that I can integrate changes as they come up: https://gist.github.com/kazcw/43c97d3924326beca87d One thing that I think is an important improvement over my initial idea is that the bloom filters don't need to be kept around and built up, they can just be one-shot and clear any matching entries from the set of known-knowns upon arrival -- provided a node is careful to ensure the txes it wants to forget are known-known-known (which isn't as bad as it sounds) to the peer it's telling it's forgetting them when the forget-filter arrives. On Thu, Jul 17, 2014 at 3:46 PM, Gavin Andresen wrote: > > A couple of half-baked thoughts: > > On Thu, Jul 17, 2014 at 5:35 PM, Kaz Wesley wrote: >> >> If there's support for this proposal, I can begin working on the specific >> implementation details, such as the bloom filters, message format, and >> capability advertisment, and draft a BIP once I have a concrete proposal for >> what those would look like and a corresponding precise cost/benefit analysis. > > > 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. > > -- > -- > Gavin Andresen Thanks Gavin, I am planning on working out the design details as I work on a prototype. I have the beginnings of a previous shot at implementing this in bitcoind to start from but my new design has some important improvements to add to that. -kaz