Updates this libraries core dependency to be on bbs-signatures which is WASM based meaning this library is now browser compatible. Note bbs-signatures has an optional dependency on node-bbs-signatures so that consumers of this library running in node environments can take advantage of the node module for the best performance.
The changes include
The top level API for signing and verifying BBS signatures is now based on Uint8Arrays instead of strings.
generateBls12381KeyPair has been renamed to generateBls12381G2KeyPair to make way for supporting G1 BLS keys.
[x] Tests for the changes have been added (for bug fixes / features)
Description
Updates this libraries core dependency to be on bbs-signatures which is WASM based meaning this library is now browser compatible. Note bbs-signatures has an optional dependency on node-bbs-signatures so that consumers of this library running in node environments can take advantage of the node module for the best performance.
The changes include
The top level API for signing and verifying BBS signatures is now based on Uint8Arrays instead of strings.
generateBls12381KeyPair
has been renamed togenerateBls12381G2KeyPair
to make way for supporting G1 BLS keys.[x] Tests for the changes have been added (for bug fixes / features)
[x] The commit message(s) follow conventional commits
[x] Documentation has been added / updated (for bug fixes / features)
[x] Changes follow the contributing document.
Motivation and Context
Supporting more of the TS and JS environment
Does this PR introduce a breaking change?
Sign and verify functions now expect the data as Uint8Array's instead of strings
Which merge strategy will you use?