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 1SfWXn-0007Iy-7K for bitcoin-development@lists.sourceforge.net; Fri, 15 Jun 2012 13:26:31 +0000 X-ACL-Warn: Received: from mail-lpp01m010-f47.google.com ([209.85.215.47]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1SfWXh-000424-KV for bitcoin-development@lists.sourceforge.net; Fri, 15 Jun 2012 13:26:31 +0000 Received: by lags15 with SMTP id s15so2258204lag.34 for ; Fri, 15 Jun 2012 06:26:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=QqM1pMu5f8bmj9PZxQfbMqkzWz86NfGcbI/oPgh/LAs=; b=YRs3mBiHsjgizT8YEalZuY/Z8xgYnqMf4U0u1H01WrAgej88O/29oR8WdkNkciyoHc 1ALOHYxaFv1QykTk9Hy2eArhyP4HOhx7iYuLeYRgPuB0aGDaR/KktSWHicdy8rCkxLj/ L0ZECQ1982Sb/hdJ5oQdyar6awi52nQrrwAnBOSDYfK4Gui9xl8Q7ZYC92g9wR0NOZTd 2mDWt/raJ43aQ7pINGlQm66LQGxHPCvC6hhl2oc++nmuzCWh9yUOaSnM3HE6TUJbU5Z9 3UHSuokZuyGwJDFQoSOdQdYz0AcYJyHhxXWWtW7AJVpVa1v20cALm+1ErtTP6ApLRG87 BYmA== MIME-Version: 1.0 Received: by 10.152.46.232 with SMTP id y8mr5594094lam.18.1339766779027; Fri, 15 Jun 2012 06:26:19 -0700 (PDT) Received: by 10.114.19.70 with HTTP; Fri, 15 Jun 2012 06:26:18 -0700 (PDT) X-Originating-IP: [2001:4830:1603:2:21c:c0ff:fe79:c8c2] In-Reply-To: References: Date: Fri, 15 Jun 2012 09:26:18 -0400 Message-ID: From: Jeff Garzik To: Mike Hearn Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQmd8s9auGHlOlGxZMbkGqwEFZQh1yE1DikHh9w3hGdYLsdWOTFEIXBeF9JBKn8jwlhpIRRW X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1SfWXh-000424-KV 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: Fri, 15 Jun 2012 13:26:31 -0000 On Thu, Jun 14, 2012 at 7:52 AM, Mike Hearn wrote: >> filterinit(false positive rate, number of elements): initialize >> filterload(data): input a serialized bloom filter table metadata and dat= a. > > Why not combine these two? This is a fair point that sipa raised. Consensus concluded that 'filterload' includes all necessary metadata required to initialize a bloom filter. That implies 'filterinit' would only be needed for 'filteradd'. If we don't think 'filteradd' has a compelling use case, filterinit + filteradd can be dropped. >> '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 =A0inv<->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. Yes, the format is something that must be hashed out (no pun intended). Need input from potential users about what information they might need. --=20 Jeff Garzik exMULTI, Inc. jgarzik@exmulti.com