New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Be consistent in using "opt_into_rbf" parameter for Opt-In RBF #10745
Conversation
Concept ACK 3187d4ed98c62a4a094d14c6df8d52dad03c7972 |
I prefer #10698. This implementation causes an unnecessary API break for bumpfee between 0.14.2 and 0.15.0 ( Your feedback in #10698 was that we shouldn't change the argument names because it'd break compatibility with a derived project. This implementation is changing those names anyway, so it seems like that's no longer an argument against #10698. |
@jnewbery This implementation is completely compatible (eg, for bumpfee). |
Also prefer #10698. Please just introduce your compatible argument names in Knots and let's stop bike shedding this and get back to doing real work. |
Yes, please stop bike shedding by trying to make this incompatible for no reason whatsoever. The other day you even said you preferred |
I actually said I liked Tying up this much time arguing about the names is ridiculous. I don't really care what name we use, but seems like everyone other than you wants to stick with |
Sigh, agree with @morcos here, do we really need a competing PR for this? We have been over this: |
This is not an interface break at all. It is completely backward compatible. |
Closing as #10698 was merged |
This is still needed, even if that means rebasing it. Please reopen. |
Essentially just #10698 done right.
Also fixes missing param name for
createrawtransaction
.