public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net,
	Amir Taaki <zgenjix@yahoo•com>
Subject: Re: [Bitcoin-development] JSON-RPC is BIP territory or not?
Date: Fri, 2 Mar 2012 14:14:05 -0500	[thread overview]
Message-ID: <201203021414.07109.luke@dashjr.org> (raw)
In-Reply-To: <1330714301.3840.YahooMailNeo@web121006.mail.ne1.yahoo.com>

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.



  reply	other threads:[~2012-03-02 19:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02 18:51 Amir Taaki
2012-03-02 19:14 ` Luke-Jr [this message]
2012-03-03 13:44 ` Stefan Thomas
2012-03-03 13:49   ` Luke-Jr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201203021414.07109.luke@dashjr.org \
    --to=luke@dashjr$(echo .)org \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=zgenjix@yahoo$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox