BIP-346: correct TxFieldSelector index upper bound#2093
Merged
Conversation
murchandamus
added
Typo-to-be-collected
Pending acceptance
Member
|
cc: @stevenroose |
jonatack
added
Fixups
jonatack
approved these changes
May 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously
parse_inout_selectiononly rejected indices strictly greater thannb_items, allowingidx == nb_itemsto pass through and later cause a panic when indexing transaction inputs/outputs.Tightened the bounds check in
parse_inout_selectionto treatidx >= nb_itemsas out of bounds, enforcing the intended0..nb_items-1index range forTxFieldSelectorindividual mode.