This repository was archived by the owner on Dec 28, 2022. It is now read-only.
Update hypercore-crypto to v3.1
#62
Merged
Conversation
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
This was referenced Nov 9, 2021
|
The changes are being incorporated into |
kasperisager
changed the title
hypercore-crypto dependency and use LE for all Merkle tree datahypercore-crypto to v3
kasperisager
changed the title
hypercore-crypto to v3hypercore-crypto to v3.1
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
All
uint64s in the Merkle tree were previously encoded as BE . This PR fixes that by upgrading tohypercore-cryptov3.1 which encodes alluint64s as LE. It's... very breaking 💥