From: "Jorge Timón" <jtimon@monetize•io>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: "Goss, Brian C., M.D." <Goss.Brian@mayo•edu>,
"bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: remove "getwork" RPC from bitcoind
Date: Tue, 20 Aug 2013 00:49:46 +0200 [thread overview]
Message-ID: <CAC1+kJNFKVrk=RQeX+NVn7Sh8RbiCeDOKNAigye9jneqO85rYA@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgQtGg+SxRc7Byw0_L3NpEudPTtBpmnKYt-+7VEVSnKZaQ@mail.gmail.com>
Removing getwork and the old miner and packaging a better miner seems
the best solution for the reasons already mentioned.
Not directly related, but this remembered me that we planned to
remove the accounting features on freicoin. We don't want to adapt
them for demurrage and we think business shouldn't use it and should
code their own accounting system instead. One that keeps a full log
of the accounting, etc.
Unfortunately the first exchange to support freicoin (cryptonit) used
this feature for accounting user balances on the exchange.
So the question is, is there any good reason to maintain this?
Is any serious business really using this or anyone at all?
I'm talking about removing the following rpc calls:
getaccount
getaddressesbyaccount
getbalance
getreceivedbyaccount
listaccounts
listreceivedbyaccount
move
sendfrom
setaccount
...and modifying these:
getnewaddress
listreceivedbyaddress
listtransactions
sendmany
I think this would also leave a cleaner API, but I'm just interested
on what the objections would be to this removal.
How crazy does this sound?
Should we reconsider their removal for freicoin, proceed or create a
pull request for bitcoin?
--
Jorge Timón
http://freico.in/
next prev parent reply other threads:[~2013-08-19 22:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 20:22 Goss, Brian C., M.D.
2013-08-19 21:07 ` Gregory Maxwell
2013-08-19 22:49 ` Jorge Timón [this message]
[not found] <mailman.167053.1376954386.4583.bitcoin-development@lists.sourceforge.net>
2013-08-21 21:24 ` Ron
2013-08-21 21:39 ` rob.golding
2013-08-22 9:36 ` Maciej Trebacz
2013-08-22 13:18 ` Jeff Garzik
2013-08-22 13:33 ` Mike Hearn
2013-08-22 15:30 ` Wladimir
-- strict thread matches above, loose matches on Subject: below --
2013-08-19 16:27 Jeff Garzik
2013-08-19 20:09 ` Frank F
2013-08-19 20:13 ` Luke-Jr
2013-08-19 20:14 ` Pieter Wuille
2013-08-19 20:16 ` Frank F
2013-08-19 20:16 ` Gregory Maxwell
2013-08-19 20:18 ` Frank F
2013-08-19 20:23 ` Gregory Maxwell
2013-08-19 20:33 ` Warren Togami Jr.
2013-08-19 20:34 ` Jeff Garzik
2013-08-19 23:02 ` Andreas Schildbach
2013-08-19 23:30 ` Warren Togami Jr.
2013-08-19 20:15 ` Matt Corallo
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='CAC1+kJNFKVrk=RQeX+NVn7Sh8RbiCeDOKNAigye9jneqO85rYA@mail.gmail.com' \
--to=jtimon@monetize$(echo .)io \
--cc=Goss.Brian@mayo$(echo .)edu \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gmaxwell@gmail$(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