Specify fees explicitly via JSON-RPC
Disables automatically adding "minimum" fees for JSON-RPC methods-- instead, it returns an error or, iff the user sets the new second parameter "force" to the 'settxfee' JSON-RPC call, sends the transaction with the user-specified fee. This second parameter to 'settxfee' is only enabled if bitcoind is started with the undocumented -nosafefees option.
Currently 4/6 support this change:
https://bitcointalk.org/index.php?topic=46925WOW, this patch actually fixes the forced TX fees annoyance (which made me make my own Bitcoin fork).
Awesome job. I guess I won't have to maintain
the fork anymore if this gets into mainline client.
