Marc Larue [ARCHIVE] on Nostr: 📅 Original date posted:2016-08-03 📝 Original message:Hi, I have 2 problems with ...
📅 Original date posted:2016-08-03
📝 Original message: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
📝 Original message: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