Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.41 as permitted sender)
	client-ip=74.125.82.41; envelope-from=gavinandresen@gmail.com;
	helo=mail-wg0-f41.google.com; 
MIME-Version: 1.0
In-Reply-To: <20120610090357.GA25567@vps7135.xlshosting.net>
References: <20120610090357.GA25567@vps7135.xlshosting.net>
Date: Mon, 11 Jun 2012 13:47:59 -0400
Message-ID: <CABsx9T3uaEBikhUo7j52mauBx0mnfk2_1mq0QOQBZVptoMB6HA@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [Bitcoin-development] BIP22/getmemorypool
Precedence: list

I think the sourceforge mailing list system had the hiccups this
weekend; sorry for Pieter's messages appearing in your inbox multiple
times, it is not his fault.

I deleted the extra copies from the mailing list archives.


As for the contents of his message, since this mailing list was not
working discussion wandered into the pull request:
  https://github.com/bitcoin/bitcoin/pull/936

Assuming this mailing list is now fixed, I'd like to pull that
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.


-- 
--
Gavin Andresen