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
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
|
Return-Path: <keatonatron@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id B51AB78D
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 3 Aug 2016 18:33:53 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qk0-f174.google.com (mail-qk0-f174.google.com
[209.85.220.174])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id BEB3715F
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 3 Aug 2016 18:33:52 +0000 (UTC)
Received: by mail-qk0-f174.google.com with SMTP id p74so211050750qka.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 03 Aug 2016 11:33:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
bh=6KikuCRqJrlZYQnPN3OQEETI0TtTVgLKBuYDze++ZPg=;
b=nHbaeO9YGTeO7fXkMvOo7gTKRYjzdFDliVdAi6vwVlj3U0h6L0Vqn6ZMDpEwjZpq9x
3htwJVaXIpPr3HmFOT9n2hg7uyfZLOZcbxEy1uU7ccr6VQPSgFeI/pEw8sz342eZ/rHm
dOXTvG0MgajNCIaA7pQnrpvr6ke+lwD+oyFqn57gSQj8Tz3r3ztl4KyUbc4O3crble4q
mdvjUjnOxU1P2i4nOSzUOe2lCnLwRux/mQ33sdP7BimAYaQvvMWy3LrQvEjpiVB2O20g
5Csum2uzTbF37arn+LzcYqrIu2Qhj9WFIgpItDc0X6/Q6Y0xomW3w/bYpCExMf9y3u74
OQoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to;
bh=6KikuCRqJrlZYQnPN3OQEETI0TtTVgLKBuYDze++ZPg=;
b=Ehe/Dnx/SE8hLiyCouDVHI1CtKb0avlQYYYfhZnwX+bK/48jWfq5lTnd+mWVT9G2bF
gurWgUnk3Tp0J+fTjKCAKwOjnGnUEqtpm/msyNY35wte8YPSNy+jqgBUU8oeYiv0imSj
ebK1voTpcqxEFWmx1zU9LSdjlE3i4zIbAooJv/utKFp+t087E1sI2k7iIupi3rSYN88e
tGGfpl0gdDpeQ/IWvoDtic4bJpt06Y6YC4JczWwQ5tUis1Rcrvt5VdQNmkdB2929FSXt
d9c5kGpQnYzysXjM1CkkintgilYcvkIG+MNqRDAbqnhFIxTgnQDdPPmvNM1XRqRmUpbB
8xvQ==
X-Gm-Message-State: AEkoouuV54MAbhTXAUQz+lUpSEG/qyAlBluyOJA0yD8tbUZva9q00MS1YrLyaytZi1TP4Ag74jcCB0ZFaYcJJQ==
X-Received: by 10.55.221.85 with SMTP id n82mr1417470qki.236.1470249231785;
Wed, 03 Aug 2016 11:33:51 -0700 (PDT)
MIME-Version: 1.0
References: <alpine.LNX.2.00.1608031152530.359@rupy.se>
In-Reply-To: <alpine.LNX.2.00.1608031152530.359@rupy.se>
From: James MacWhyte <macwhyte@gmail.com>
Date: Wed, 03 Aug 2016 18:33:41 +0000
Message-ID: <CAH+Axy5jSRVbAw_MaJArYp9_nTB8Ws6QZ5hoq4rfBZw80RciFA@mail.gmail.com>
To: Marc Larue <marc@rupy.se>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a1149d1de31259e05392f135a
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Fees and Accounts
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2016 18:33:53 -0000
--001a1149d1de31259e05392f135a
Content-Type: text/plain; charset=UTF-8
From what I've seen, most people build their own account system separately
(including fee management) and just use bitcoind to send, receive, and
verify transactions. It's not meant to be a drop-in solution for running an
entire bitcoin deposit and withdrawal system, it just provides the bare
tools required to build your own. If you need a pre-built solution, there
are companies that provide those types of services as a platform (BitGo,
for example).
On Wed, Aug 3, 2016, 11:25 Marc Larue via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hi,
>
> I have 2 problems with bitcoind that separately are not a problem but
> together they make the platform unusable for many projects.
>
> If I have accounts I need to make sure the account holders do not
> overcharge their account. To do this I can now use "createrawtransaction()
> + fundrawtransaction() + signrawtransaction()" and then make sure the
> transaction can be paid by an account.
>
> But since you deprecated the accounts and there is no
> sendrawtransactionfrom() method; I either have to build my own account
> system (this is no picknick btw, since you need to track all incoming
> funds to all addresses and having an integrated account system in bitcoind
> is 100% necessary to do this effectively).
>
> Or I might be able to go ahead and speculate that you will not be able to
> untangle the account code and hack my bitcoind to have a sendfrom with a
> fixed fee parameter that overrides the size multiplication and I just do
> the math before I send hoping that the transactions go through (this is
> bad but better than having accounts overcharge because they send dust that
> induce high fees).
>
> I understand the privacy problems with using accounts for off-chain
> microstransactions but currently it's the best workable option.
>
> I hope you understand that I'm not trolling here, I have been mining since
> 2011 on FPGAs and built bitcoinbankbook.com 2 years ago. When I descovered
> that once transactions will require fees (back then they didn't) and that
> your system is not able to handle fees with accounts, I stopped developing
> everything related to bitcoin.
>
> There are probably 100s if not 1000s of developers in the same situation.
>
> You can't just deprecate accounts like that because nobody likes the code.
> Without accounts bitcoind is only a person-to-person manual client.
>
> To build many-to-many automatic "organisations" on top of bitcoind you
> need accounts and you need fees that are predictable.
>
> Kind Regards,
>
> /marc
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--001a1149d1de31259e05392f135a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr">From what I've seen, most people build their own account=
system separately (including fee management) and just use bitcoind to send=
, receive, and verify transactions. It's not meant to be a drop-in solu=
tion for running an entire bitcoin deposit and withdrawal system, it just p=
rovides the bare tools required to build your own. If you need a pre-built =
solution, there are companies that provide those types of services as a pla=
tform (BitGo, for example).</p>
<br><div class=3D"gmail_quote"><div dir=3D"ltr">On Wed, Aug 3, 2016, 11:25 =
Marc Larue via bitcoin-dev <<a href=3D"mailto:bitcoin-dev@lists.linuxfou=
ndation.org">bitcoin-dev@lists.linuxfoundation.org</a>> wrote:<br></div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi,<br>
<br>
I have 2 problems with bitcoind that separately are not a problem but<br>
together they make the platform unusable for many projects.<br>
<br>
If I have accounts I need to make sure the account holders do not<br>
overcharge their account. To do this I can now use "createrawtransacti=
on()<br>
+ fundrawtransaction() + signrawtransaction()" and then make sure the<=
br>
transaction can be paid by an account.<br>
<br>
But since you deprecated the accounts and there is no<br>
sendrawtransactionfrom() method; I either have to build my own account<br>
system (this is no picknick btw, since you need to track all incoming<br>
funds to all addresses and having an integrated account system in bitcoind<=
br>
is 100% necessary to do this effectively).<br>
<br>
Or I might be able to go ahead and speculate that you will not be able to<b=
r>
untangle the account code and hack my bitcoind to have a sendfrom with a<br=
>
fixed fee parameter that overrides the size multiplication and I just do<br=
>
the math before I send hoping that the transactions go through (this is<br>
bad but better than having accounts overcharge because they send dust that<=
br>
induce high fees).<br>
<br>
I understand the privacy problems with using accounts for off-chain<br>
microstransactions but currently it's the best workable option.<br>
<br>
I hope you understand that I'm not trolling here, I have been mining si=
nce<br>
2011 on FPGAs and built <a href=3D"http://bitcoinbankbook.com" rel=3D"noref=
errer" target=3D"_blank">bitcoinbankbook.com</a> 2 years ago. When I descov=
ered<br>
that once transactions will require fees (back then they didn't) and th=
at<br>
your system is not able to handle fees with accounts, I stopped developing<=
br>
everything related to bitcoin.<br>
<br>
There are probably 100s if not 1000s of developers in the same situation.<b=
r>
<br>
You can't just deprecate accounts like that because nobody likes the co=
de.<br>
Without accounts bitcoind is only a person-to-person manual client.<br>
<br>
To build many-to-many automatic "organisations" on top of bitcoin=
d you<br>
need accounts and you need fees that are predictable.<br>
<br>
Kind Regards,<br>
<br>
/marc<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>
--001a1149d1de31259e05392f135a--
|
