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 1SeOgT-00035G-I2 for bitcoin-development@lists.sourceforge.net; Tue, 12 Jun 2012 10:50:49 +0000 X-ACL-Warn: Received: from vps7135.xlshosting.net ([178.18.90.41]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1SeOgS-0007py-MR for bitcoin-development@lists.sourceforge.net; Tue, 12 Jun 2012 10:50:49 +0000 Received: by vps7135.xlshosting.net (Postfix, from userid 1000) id A4567244A4A; Tue, 12 Jun 2012 12:50:41 +0200 (CEST) Date: Tue, 12 Jun 2012 12:50:40 +0200 From: Pieter Wuille To: thomasV1@gmx.de Message-ID: <20120612105038.GA29784@vps7135.xlshosting.net> References: <20120610090357.GA25567@vps7135.xlshosting.net> <20120611181022.10710@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120611181022.10710@gmx.net> X-PGP-Key: http://sipa.ulyssis.org/pubkey.asc User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: 1.2 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (pieter.wuille[at]gmail.com) 0.0 DKIM_ADSP_CUSTOM_MED No valid author signature, adsp_override is CUSTOM_MED -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 1.2 NML_ADSP_CUSTOM_MED ADSP custom_med hit, and not from a mailing list X-Headers-End: 1SeOgS-0007py-MR Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] BIP22/getmemorypool 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: Tue, 12 Jun 2012 10:50:49 -0000 On Mon, Jun 11, 2012 at 08:10:22PM +0200, thomasV1@gmx.de wrote: > > > discussion back here. The executive summary: Pieter and I feel like > > BIP 22 is overly complicated, and would like it to be simpler. I'd > > especially like to hear what people think will be the "will be used by > > lots of pool customers" features and what are the "will be used by > > less than 5% of pool customers" features. > > will be used by Electrum servers Please. This is not about whether getmemorypool is useful (at least I am a big fan of BIP22's big picture). It's about whether it needs 20 optional features. -- Pieter