fix: correct array indexing in commitment functions to prevent out-of-bounds access #88
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.
Fix array index calculation in three commitment functions that were causing
potential out-of-bounds access when storing the last element:
The issue was that the index calculation was using the array size instead of
size - 1 for the last element position. This could lead to runtime errors
with certain input sizes.
Also fix typo in compute_merkle_root comment (removed duplicate "the").