This doesn't change functionality beyond improving the --help tdocumentation.
Together with #16770 , this allows to get rid of Params().IsTestChain().
This is an alternative to #16524 , which, for example @instagibbs doesn't seem to like very much.
This doesn't change functionality beyond improving the --help tdocumentation.
Together with #16770 , this allows to get rid of Params().IsTestChain().
This is an alternative to #16524 , which, for example @instagibbs doesn't seem to like very much.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
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.
4444 | + } 4445 | + walletInstance->m_fallback_fee = CFeeRate(nFeePerK); 4446 | + walletInstance->m_allow_fallback_fee = nFeePerK != 0; //disable fallback fee in case value was set to 0, enable if non-null value 4447 | + 4448 | if (gArgs.IsArgSet("-discardfee")) { 4449 | CAmount nFeePerK = 0;
This nFeePerK is shadowing the nFeePerK in the outer scope.
Yes, it is. And more of the same below. But in every use of their own nFeePerK they initialize it. Anyway, what do you think I should do? Perhaps just rename the variable? any suggestion on the name?
I would use another variable name to disambiguate :)
Fixed nit, renamed to fee_per_k.