Bitcoin RPC interface: sendfrom & tx fee

[Artefact2]

Is it possible to explicitly set the transaction fee when transferring bitcoins with the "sendfrom" command ?

Also, is it possible to force the client to take the transaction fee only from the <from> account, and not from any other account ? The default behavior is very annoying in an application where every user has an account on the same wallet, and can transfer coins from/to it.

[1714982476]

1714982476

[1714982476]

1714982476

[winnetou]

Also, is it possible to force the client to take the transaction fee only from the <from> account, and not from any other account ? The default behavior is very annoying in an application where every user has an account on the same wallet, and can transfer coins from/to it.

+1

[vv01f]

1. No, not in a single command. You'd need two commands.
2. Fees are taken from the sender as far as I understand?! Account is wallet in my mind, an account may have many many addresses, but thats checkable. Also other accounts may be listet with an address in your addressbook, but not your own account.

To set you transaction fee (even to zero) you need to start the client as server/daemon. read on that and list the help of that daemon to go on.
The same way you'll find how to check if an address is belonging to your account and e.g. list the addressbook.


have fun!

[kjj]

In my opinion, the whole account system needs to be removed from the code.  You really should stop using it.

Just track who you give addresses to, and who initiates sends.

[d'aniel]

In my opinion, the whole account system needs to be removed from the code.  You really should stop using it.

If the client could better handle multiple wallets, would this achieve exactly the same purpose as accounts?

[kjj]

In my opinion, the whole account system needs to be removed from the code.  You really should stop using it.

If the client could better handle multiple wallets, would this achieve exactly the same purpose as accounts?

No, you don't need multiple wallets, or multiple accounts, or anything fancy.  You just need to take notes whenever you give out an address, and whenever you spend.

[2112]

In my opinion, the whole account system needs to be removed from the code.  You really should stop using it.

This is very wise opinion. From the accounting/auditing point of view the present wallet model is badly broken. Transactions should be stored in a sequential csv file that is instantly usable by any of the accounting packages for businesses or consumers.

Since the wallet.dat database is essentially append-only this would be relatively simple modification to the existing code. Berkeley DB already supports flat-text database files, but the database model need to be changed from Btree to RecNo.