1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jtimon@monetize.io>) id 1VBYMW-0005qj-DE
for bitcoin-development@lists.sourceforge.net;
Mon, 19 Aug 2013 22:55:48 +0000
Received: from mail-lb0-f169.google.com ([209.85.217.169])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VBYMU-0005R0-Io
for bitcoin-development@lists.sourceforge.net;
Mon, 19 Aug 2013 22:55:48 +0000
Received: by mail-lb0-f169.google.com with SMTP id u10so3565163lbi.0
for <bitcoin-development@lists.sourceforge.net>;
Mon, 19 Aug 2013 15:55:39 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=K6ELTgzVe9fpDj182lCDYI0cmAkC/6r0wGEuxdINCcU=;
b=kGj1KRqRsR/y+1giWmddpAYYPku32pg9gkjTcFbV8mKh9b9SPndLgzFUgXql18og1u
cNwZGkIAWheVToIXxAkgOBlcD6zNbi7PWO1C+Q1/vl6Nua0pitEqYNMYZUeVUbLqXfn8
yxIz0Mm3IFQs1Xmu5beDEzPUHOlVirls9ZgHwPQvowwbO6vt8mPhpaDMiTR5E+FWm+x2
7251QNjCauVSwYBIM4Gna045mHIXSZ6yH9JStpvVS+RPHaM4oRqZv33WhiqhL2ceXvJt
yiYkp1ohtqTYgPhZzDPLUQPB89Wt6AWppCyzQSJmnmhg962E5fy6iDhQbEei2VaSCFp8
lahA==
X-Gm-Message-State: ALoCoQnnU1z4/d0U8VWEqGKDIcy2IFpjI3dEfDTrFNDckHQvD9ZzTc2u1C9czp/3b69nIIXuzWvF
MIME-Version: 1.0
X-Received: by 10.152.120.73 with SMTP id la9mr13971716lab.3.1376952586874;
Mon, 19 Aug 2013 15:49:46 -0700 (PDT)
Received: by 10.112.40.15 with HTTP; Mon, 19 Aug 2013 15:49:46 -0700 (PDT)
X-Originating-IP: [85.53.141.115]
In-Reply-To: <CAAS2fgQtGg+SxRc7Byw0_L3NpEudPTtBpmnKYt-+7VEVSnKZaQ@mail.gmail.com>
References: <FFE335820B1BFF4F8E8619F446F2D87F4C1A2E7B@MSGPEXCEI26B.mfad.mfroot.org>
<CAAS2fgQtGg+SxRc7Byw0_L3NpEudPTtBpmnKYt-+7VEVSnKZaQ@mail.gmail.com>
Date: Tue, 20 Aug 2013 00:49:46 +0200
Message-ID: <CAC1+kJNFKVrk=RQeX+NVn7Sh8RbiCeDOKNAigye9jneqO85rYA@mail.gmail.com>
From: =?ISO-8859-1?Q?Jorge_Tim=F3n?= <jtimon@monetize.io>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1VBYMU-0005R0-Io
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
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 22:55:48 -0000
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?
--=20
Jorge Tim=F3n
http://freico.in/
|
