From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1X7uS5-0000Wj-8X for bitcoin-development@lists.sourceforge.net; Thu, 17 Jul 2014 22:47:01 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.54 as permitted sender) client-ip=209.85.213.54; envelope-from=gavinandresen@gmail.com; helo=mail-yh0-f54.google.com; Received: from mail-yh0-f54.google.com ([209.85.213.54]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1X7uS3-0001Xm-DM for bitcoin-development@lists.sourceforge.net; Thu, 17 Jul 2014 22:47:01 +0000 Received: by mail-yh0-f54.google.com with SMTP id v1so1786613yhn.41 for ; Thu, 17 Jul 2014 15:46:53 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.236.172.161 with SMTP id t21mr545554yhl.65.1405637212983; Thu, 17 Jul 2014 15:46:52 -0700 (PDT) Received: by 10.170.190.208 with HTTP; Thu, 17 Jul 2014 15:46:52 -0700 (PDT) In-Reply-To: References: Date: Thu, 17 Jul 2014 18:46:52 -0400 Message-ID: From: Gavin Andresen To: Kaz Wesley Content-Type: multipart/alternative; boundary=20cf304273e0c3595204fe6b6af3 X-Spam-Score: -0.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 (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -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: 1X7uS3-0001Xm-DM 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 22:47:01 -0000 --20cf304273e0c3595204fe6b6af3 Content-Type: text/plain; charset=ISO-8859-1 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 --20cf304273e0c3595204fe6b6af3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
A co= uple of half-baked thoughts:

On Thu, Jul 17, 2014 at 5:35 PM, Kaz Wesley <keziah= w@gmail.com> wrote:
If there's support for this proposa= l, I can begin working on the specific
implementation details, su= ch as the bloom filters, message format, and
capability advertisment, and draft a BIP once I have a concrete propos= al for
what those would look like and a corresponding precise cost/benefit an= alysis.

I'd encourage you to code up a prototy= pe first (or at the same time), in whatever programming language / networki= ng library you're most familiar with.

Maybe not e= ven 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 &quo= t;broadcast as many near-miss blocks as bandwidth will allow" on a min= ing backbone network should allow insanely fast propagation of most newly s= olved blocks.

--
--
Gavin Andresen

--20cf304273e0c3595204fe6b6af3--