📅 Original date posted:2012-03-02
📝 Original message: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.
Luke-Jr [ARCHIVE] /
npub1dt…u7wrs
2023-06-07 03:11:05
in reply to nevent1q…yvzr
Author Public Key
npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrsPublished at
2023-06-07 03:11:05Event JSON
{
"id": "7384afe728dee42cfcc557856de8e4b9ed73e2e96c8825b1425e22a15b5e330b",
"pubkey": "6ac6a519b554d8ff726a301e3daec0b489f443793778feccc6ea7a536f7354f1",
"created_at": 1686107465,
"kind": 1,
"tags": [
[
"e",
"2e5e8dd3265b5e600cefae61162279031c2b2b91b73991e9dbfd27a9a299ba97",
"",
"root"
],
[
"e",
"ab9ad406454245f70b4be7868da00cd7d738d59c23b22928ff3142793aa9c060",
"",
"reply"
],
[
"p",
"c86b2a2e41d61aaf7ab7198ba65cf5a35c015f3117a71eaba5e19bb537b20051"
]
],
"content": "📅 Original date posted:2012-03-02\n📝 Original message:On Friday, March 02, 2012 1:51:41 PM Amir Taaki wrote:\n\u003e It is a implementation-specific non-bitcoin-protocol proposal. My\n\u003e understanding of BIPs is that they apply across bitcoin implementations\n\u003e and largely focus on the most generic use-cases (like the URIs) and the\n\u003e protocol. Things which affect all clients, and allow the system to\n\u003e function as a united whole.\n\nThis isn't implementation-specific. If you read it, you should notice it is \nintentionally generic for multiple use-cases. Right now bitcoind supports \ngetmemorypool for a few use cases, but this proposed BIP enables it to be \nutilized for many more. Specifically, Eligius and at least a few other pools \nwish to move toward a more decentralized method of pooled mining (similar to \nthe proprietary p2pool protocol). Eligius already supports miners producing \ntheir own work with getmemorypool using this draft, and our Eloipool server is \nopen source (AGPL-3) for others to adopt (I know of at least one other pool \nplanning to do so). Other pools not using Eloipool also have expressed \ninterest in this, so a standard is desirable.",
"sig": "4b49fa6c32ac4d981e0b0aa04dfc41d2b6e20504bf3990bee5497744996b2f300f16d979692e3ff49f462b124fdf5ae6cab5c8c18a04952fb64126e331217944"
}