Specify fees explicitly via JSON-RPC #1645

pull luke-jr wants to merge 4 commits into bitcoin:master from luke-jr:force_send changing 7 files +92 −34

luke-jr commented at 8:46 PM on August 1, 2012: member

Status: Deferred until handling stuck transactions is implemented

If a transaction sent requires a fee greater than (new) maxtxfee option, aborts with an error.

If started with undocumented unsupported -nosafefees option, allows JSON-RPC to set a "forcetxfee" to override the error and send anyway (with maxtxfee amount of fees only).
Don't automatically include fees via JSON-RPC, and (with undocumented -nosafefees option) allow forcing them to send with under the 'minimum' 65c7141731
Accept automatic fees up to new "maxtxfee" parameter fff1f424c6
Accept any transaction (fee-free or even non-standard) from myself 97412a5463
Refactor maxtxfee and -nosafefees slightly to work together eb130ae647
jgarzik commented at 9:41 PM on August 2, 2012: contributor
Closing,
1. requires nak'd commit that accepts non-standard transactions
2. "status: deferred" could be for a long time
3. this is an active area of Gavin work too, and so I think it is fair to require some discussion (on bitcoin-devel?) before proposing fee calculation or fee RPC changes. You will note that #1647 is on the list for 0.7, so hopefully that illustrates we are being fair in this area, and merging discussed items.
jgarzik closed this on Aug 2, 2012
luke-jr commented at 12:56 AM on August 3, 2012: member
1. It was not NAK'd.
2. So?
3. It was not at the time it was implemented, and still isn't really. Low-level tools are no substitute for the high-level ones.
DrahtBot locked this on Sep 8, 2021

Contributors

luke-jr

jgarzik