allow feerate argument in bumpfee
in addition to confTarget
#16203
issue
instagibbs
openend this issue on
June 13, 2019
-
instagibbs commented at 1:31 pm on June 13, 2019: memberIf someone has their own home-grown fee estimator, let’s allow them to use it on command line.
-
fanquake added the label RPC/REST/ZMQ on Jun 13, 2019
-
instagibbs commented at 3:44 pm on July 11, 2019: memberWas hoping someone newer would tackle this, I think it’s a pretty easy change :)
-
MarcoFalke added the label good first issue on Jul 11, 2019
-
ezegom commented at 0:20 am on July 12, 2019: contributor
Was hoping someone newer would tackle this, I think it’s a pretty easy change :)
I’ll take a look at this issue :)
-
instagibbs commented at 8:19 pm on July 22, 2019: member@ezegom I wasn’t able to log in to my irc for a bit, sorry if I missed a message
-
ezegom commented at 7:32 pm on July 29, 2019: contributor
@instagibbs @Sjors @MarcoFalke Quick question I was taking a look at @Sjors code for
signerbumpfee
which also allows the user to specify a feeRate. https://github.com/bitcoin/bitcoin/blob/428dfe0e670be210cb774877a04b24f117ff892f/src/wallet/rpcsigner.cpp#L161-L164The
signerbumpfee
rpc eventually callsCreateRateBumpTransaction
, which calculates the feeRate to be used as the max between the feeRate passed (minFeeRate) and the old_fee + incrementalRelayFee (feeRate). Thus the feeRate provided by the user is only used if it is larger thanold_fee+incrementalRelayFee
https://github.com/bitcoin/bitcoin/blob/428dfe0e670be210cb774877a04b24f117ff892f/src/wallet/feebumper.cpp#L253-L257The implementation I’ve worked on, always creates the transaction using the feeRate passed in unless the feeRate is invalid. To check whether the feeRate passed in is valid or not, I’ve made a helper method that follows the same logic used to check the fee for when the TotalFee argument is used.
My question is: What is the desired behavior if the user entered a feeRate that is lower than the old_fee + incrementalRelayFee? Should we:
- Display error notifying the user that the fee is too small
- Use the old_fee + incrementalRelayFee as our feeRate (as @Sjors does)
- Use the feeRate passed in by the user unless its less than the old_fee or greater than the wallet’s maximum fee.
-
instagibbs commented at 8:35 pm on July 29, 2019: memberI’d have to understand more what the implementation looks like, but if a feerate is given, I’d expect it to either pass or fail, not do a fallback. (option 1)
-
MarcoFalke commented at 9:12 pm on July 29, 2019: memberI think any option is fine, as long as it is documented and the behavior is the same in
signerbumpfee
andbumpfee
-
ezegom commented at 1:07 am on July 30, 2019: contributor@instagibbs, @MarcoFalke : I’ve made a draft PR. Any feedback is greatly appreciated!
-
instagibbs commented at 2:06 pm on October 2, 2019: memberNow merged in master, slated for 0.19, closing
-
instagibbs closed this on Oct 2, 2019
-
MarcoFalke locked this on Dec 16, 2021
This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2024-11-17 12:12 UTC
More mirrored repositories can be found on mirror.b10c.me