rpc: Uncouple non-wallet rpcs from maxTxFee global#15620
rpc: Uncouple non-wallet rpcs from maxTxFee global#15620maflcko merged 3 commits intobitcoin:masterfrom
Conversation
|
Concept ACK! |
|
utACK fa96d76. Verified this replaces the only usages of |
|
How about bitcoin/src/wallet/feebumper.cpp Lines 161 to 166 in 93623ee 😮 space in L162 |
|
Bumpfee is a wallet function, so it's reasonable if it continues to use maxtxfee if maxtxfee becomes a wallet option. |
promag
left a comment
There was a problem hiding this comment.
Misinterpreted the goal sorry, IMO could have the title Uncouple non-wallet rpcs from maxTxFee global.
Agree with adding release notes.
|
Renamed title and added release notes as requested by @promag |
ryanofsky
left a comment
There was a problem hiding this comment.
utACK faadaae4795038d77936f36483f1410cd92b3238, only change is release notes
fa55499 to
fa4230b
Compare
jnewbery
left a comment
There was a problem hiding this comment.
Oops. I'd already written a branch for this too.
One comment inline, otherwise utACK fa4230b8a708ad9b848c97a5142da804afc43a4b.
fa4230b to
fa1ad20
Compare
|
Changed my mind as requested by @jnewbery |
|
utACK fa1ad20 |
|
utACK fa1ad20 |
|
Concept ACK |
|
utACK fa1ad20 |
fa1ad20 doc: Add release notes for 15620 (MarcoFalke) fa96d76 rpc: Uncouple rpcs from maxTxFee global (MarcoFalke) fa965e0 rpc: 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 bitcoin#15355 * [RFC] Long term plan for wallet command-line args bitcoin#13044 ACKs for commit fa1ad2: jnewbery: utACK fa1ad20 Empact: utACK bitcoin@fa1ad20 jnewbery: utACK fa1ad20 promag: utACK fa1ad20. Tree-SHA512: c9cf0b54cd30ff3ab0d090b072cc38fcbb2840bc6ad9a9711995333bc927d2500aece6b5a60e061666eca5ed72b70aa318d21e51eb15ee0106b41f5b6e4e1adf
5c759c7 [wallet] Move maxTxFee to wallet (John Newbery) Pull request description: Closes bitcoin#15355 Moves the `-maxtxfee` from the node to the wallet. See discussion in issue for details. This is a cleanup. There is no change in behaviour. Completes bitcoin#15620 ACKs for commit 5c759c: MarcoFalke: utACK 5c759c7 ryanofsky: utACK 5c759c7. Changes since last review: updated commit message and an error message and method name. meshcollider: utACK bitcoin@5c759c7 Tree-SHA512: 2f9b2729da3940a5cda994d3f3bc11ee1a52fcc1c5e9842ea0ea63e4eb0300e8416853046776311298bc449ba07554aa46f0f245ce28598a5b0bd7347c12e752
Summary: * rpc: Use IsValidNumArgs over hardcoded size checks * rpc: Uncouple rpcs from maxTxFee global * doc: Add release notes for 15620 This is a backport of Core [[bitcoin/bitcoin#15620 | PR15620]] Test Plan: ninja all check-all Reviewers: #bitcoin_abc, jasonbcox Reviewed By: #bitcoin_abc, jasonbcox Differential Revision: https://reviews.bitcoinabc.org/D6266
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
-maxtxfeeto the wallet.See also related discussions:
-maxtxfeeshould not be used by both node and wallet-maxtxfeeshould not be used by both node and wallet #15355