Since commit 91f6d2bc8ff4d4cd1b86daa370ec9d2d9662394d in 2020, the wallet accepts and documents conf_target for the fee bump RPC.
So it seems time to cut the confusion and properly deprecate it with the next cycle.
Since commit 91f6d2bc8ff4d4cd1b86daa370ec9d2d9662394d in 2020, the wallet accepts and documents conf_target for the fee bump RPC.
So it seems time to cut the confusion and properly deprecate it with the next cycle.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline and AI policy for information on the review process.
| Type | Reviewers |
|---|---|
| ACK | fametrano |
If your review is incorrectly listed, please copy-paste <code><!--meta-tag:bot-skip--></code> into the comment that the bot should ignore.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
encryptwallet RPC for encrypting existing wallets. by davidgumberg)If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
tACK fab22ac42e350d4b4481515fe8ba2a319a744389
No test checks that confTarget still works under -deprecatedrpc=confTarget. The comment in rpc_deprecated.py asks that each deprecation tested there keep another functional test that still exercises it under the flag. wallet_bumpfee.py gains the flag, but its only confTarget call is the "should not both be set" error, so a change that broke confTarget behind the flag would still pass the tests. One bumpfee and one psbtbumpfee call with {"confTarget": 6} in that test would cover it.
The rest matched. Without the flag, both RPCs return -32 for confTarget, alone or next to conf_target, before the txid is looked up. With the flag, confTarget bumps and the conflict error is unchanged. conf_target works either way, positional or named. The help and getopenrpcinfo list only conf_target.
I measured this on regtest against a build of the head, with and without the flag, with calls sent through a client library I maintain. I can share the script and its output.
No test checks that
confTargetstill works under-deprecatedrpc=confTarget.
Your LLM-co-authored comment is just repeating what the Ralph LLM already said. There never was a test for this since 2020, the option was undocumented since then, so likely no user is using it. I don't think it makes sense to add a test for this now, given that such a test would be harder to review than the code change here by itself.