fix: bump order in BEEF creation #59
Merged
+4
−4
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.
This implementation fixes a problem related to randomly writing BUMPs to the BEEF Hex
As stated in the documentation:
When iterating over a map with a range loop, the iteration order is not specified and is not guaranteed to be the same from one iteration to the next.
This pull request includes changes to the
BEEF
method in thetransaction/beef.go
file to improve the handling ofMerklePath
objects. The most important changes include switching from a map to a slice forbumps
and adjusting the logic to use the new data structure.Improvements to
BEEF
method:bumps
variable from a map to a slice of*MerklePath
to simplify the data structure.bumpIndex
for tracking indices in thebumps
slice, replacing the previous map-based approach.