feat: add noble-based impl for fallback when BigInt is available #210
Conversation
This file contains 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
ChALkeR
force-pushed
the
chalker/noble
branch
from
f2f4072 to
a9356eb
Compare
ChALkeR
changed the title
ChALkeR
force-pushed
the
chalker/noble
branch
3 times, most recently
from
42a1549 to
3c5ae17
Compare
ChALkeR
force-pushed
the
chalker/noble
branch
from
3c5ae17 to
99a398c
Compare
|
Refactored code a bit for better unification with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Uses
@noble/secp256k1-based implementation by default when bindings are unavailable but BigInt is availableIf neither bindings nor BigInt are available, falls back to elliptic-based implementation
Entry point
secp256k1/elliptic.jsremainsThis should be a non-breaking change