Specify fees explicitly via JSON-RPC #1645
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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).