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-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Sf8bR-0003Wk-4d for bitcoin-development@lists.sourceforge.net; Thu, 14 Jun 2012 11:52:41 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.53 as permitted sender) client-ip=74.125.82.53; envelope-from=mh.in.england@gmail.com; helo=mail-wg0-f53.google.com; Received: from mail-wg0-f53.google.com ([74.125.82.53]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Sf8bL-0003fX-Ob for bitcoin-development@lists.sourceforge.net; Thu, 14 Jun 2012 11:52:41 +0000 Received: by wgbfm10 with SMTP id fm10so1494472wgb.10 for ; Thu, 14 Jun 2012 04:52:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.8.69 with SMTP id p5mr46113715wia.17.1339674749591; Thu, 14 Jun 2012 04:52:29 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.216.254.232 with HTTP; Thu, 14 Jun 2012 04:52:29 -0700 (PDT) In-Reply-To: References: Date: Thu, 14 Jun 2012 13:52:29 +0200 X-Google-Sender-Auth: nzEI0TPjOU1Krm2FfLAjUU5mXuE Message-ID: From: Mike Hearn To: Jeff Garzik Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.5 (-) 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 (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 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: 1Sf8bL-0003fX-Ob Cc: Bitcoin Development Subject: Re: [Bitcoin-development] New P2P commands for diagnostics, SPV clients 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, 14 Jun 2012 11:52:41 -0000 > filterinit(false positive rate, number of elements): initialize > filterload(data): input a serialized bloom filter table metadata and data. Why not combine these two? > 'filterload' and 'filteradd' enable special behavior changes for > 'mempool' and existing P2P commands, whereby only transactions > matching the bloom filter will be announced to the connection, and > only matching transactions will be sent inside serialized blocks. Need to specify the format of how these arrive. It means that when a new block is found instead of inv<->getdata<->block we'd see something like inv<->getdata<->merkleblock where a "merkleblock" structure is a header + list of transactions + list of merkle branches linking them to the root. I think CMerkleTx already knows how to serialize this, but it redundantly includes the block hash which would not be necessary for a merkleblock message.