From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net, Amir Taaki <zgenjix@yahoo.com>
Date: Fri, 2 Mar 2012 14:14:05 -0500
User-Agent: KMail/1.13.7 (Linux/3.2.2-gentoo; KDE/4.7.4; x86_64; ; )
References: <1330714301.3840.YahooMailNeo@web121006.mail.ne1.yahoo.com>
In-Reply-To: <1330714301.3840.YahooMailNeo@web121006.mail.ne1.yahoo.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201203021414.07109.luke@dashjr.org>
Subject: Re: [Bitcoin-development] JSON-RPC is BIP territory or not?
Precedence: list

On Friday, March 02, 2012 1:51:41 PM Amir Taaki wrote:
> It is a implementation-specific non-bitcoin-protocol proposal. My
> understanding of BIPs is that they apply across bitcoin implementations
> and largely focus on the most generic use-cases (like the URIs) and the
> protocol. Things which affect all clients, and allow the system to
> function as a united whole.

This isn't implementation-specific. If you read it, you should notice it is 
intentionally generic for multiple use-cases. Right now bitcoind supports 
getmemorypool for a few use cases, but this proposed BIP enables it to be 
utilized for many more. Specifically, Eligius and at least a few other pools 
wish to move toward a more decentralized method of pooled mining (similar to 
the proprietary p2pool protocol). Eligius already supports miners producing 
their own work with getmemorypool using this draft, and our Eloipool server is 
open source (AGPL-3) for others to adopt (I know of at least one other pool 
planning to do so). Other pools not using Eloipool also have expressed 
interest in this, so a standard is desirable.