-
Notifications
You must be signed in to change notification settings - Fork 38.7k
Remove unused feebumper code #24562
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
Remove unused feebumper code #24562
The head ref may contain hidden characters: "2203-remFeeBumpCode-\u{1F407}"
Conversation
|
Can be tested in the GUI Console with: |
promag
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code review ACK fae5d06
Indeed, input sequence is set in CreateTransactionInternal:
Lines 805 to 813 in 7b83c7d
| // BIP125 defines opt-in RBF as any nSequence < maxint-1, so | |
| // we use the highest possible value in that range (maxint-2) | |
| // to avoid conflicting with other possible uses of nSequence, | |
| // and in the spirit of "smallest possible change from prior | |
| // behavior." | |
| const uint32_t nSequence{coin_control.m_signal_bip125_rbf.value_or(wallet.m_signal_rbf) ? MAX_BIP125_RBF_SEQUENCE : CTxIn::MAX_SEQUENCE_NONFINAL}; | |
| for (const auto& coin : selected_coins) { | |
| txNew.vin.push_back(CTxIn(coin.outpoint, CScript(), nSequence)); | |
| } |
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsReviewers, 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. |
|
ACK fae5d06 |
|
cc @instagibbs |
This reverts commit ddbd96a.
This was accidentally added in commit 0ea47ba. Presumably due to a copy-paste error, as
CreateTransactionalready takes care of the rbf-signal.