mirror of
https://github.com/bitcoin/bitcoin.git
synced 2026-04-20 11:49:07 +02:00
Merge #15620: rpc: Uncouple non-wallet rpcs from maxTxFee global
fa1ad200d3doc: Add release notes for 15620 (MarcoFalke)fa96d76421rpc: Uncouple rpcs from maxTxFee global (MarcoFalke)fa965e03c7rpc: Use IsValidNumArgs over hardcoded size checks (MarcoFalke) Pull request description: This makes the rpcs a bit more stateless by falling back to their own default max fee instead of the global maxTxFee. A follow up pull request will move `-maxtxfee` to the wallet. See also related discussions: * `-maxtxfee` should not be used by both node and wallet #15355 * [RFC] Long term plan for wallet command-line args #13044 ACKs for commit fa1ad2: jnewbery: utACKfa1ad200d3Empact: utACKfa1ad200d3jnewbery: utACKfa1ad200d3promag: utACKfa1ad20. Tree-SHA512: c9cf0b54cd30ff3ab0d090b072cc38fcbb2840bc6ad9a9711995333bc927d2500aece6b5a60e061666eca5ed72b70aa318d21e51eb15ee0106b41f5b6e4e1adf
This commit is contained in:
13
doc/release-notes-15620.md
Normal file
13
doc/release-notes-15620.md
Normal file
@@ -0,0 +1,13 @@
|
||||
Updated RPCs
|
||||
------------
|
||||
|
||||
* The -maxtxfee setting no longer has any effect on non-wallet RPCs.
|
||||
|
||||
The `sendrawtransaction` and `testmempoolaccept` RPC methods previously
|
||||
accepted an `allowhighfees` parameter to fail the mempool acceptance in case
|
||||
the transaction's fee would exceed the value of the command line argument
|
||||
`-maxtxfee`. To uncouple the RPCs from the global option, they now have a
|
||||
hardcoded default for the maximum transaction fee, that can be changed for
|
||||
both RPCs on a per-call basis with the `maxfeerate` parameter. The
|
||||
`allowhighfees` boolean option has been removed and replaced by the
|
||||
`maxfeerate` numeric option.
|
||||
Reference in New Issue
Block a user