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. ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
