feat: switch to use bbs-signatures #19
Merged
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
tplooker
force-pushed
the
tl/wasm-support
branch
from
4f83eb5 to
fc29128
Compare
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.
Description
Shifts to using bbs-signatures instead of node-bbs-signatures. This means the library can be used in browser and react native environments.
The un-resolved question is centered around why tests need to be executed in node environments (see here)
Also blocked by a stable release for bbs-signatures
Resolves #13
Motivation and Context
Greater support of the TS/JS ecosystem
Does this PR introduce a breaking change?
Which merge strategy will you use?