digitalbazaar / bbs-signatures Goto Github PK

This additional interface would receive data to be signed / verified as a string of bytes (using Uint8Array) that contain serialized parameters such as header, messages, etc. using the serialization primitives defined by the BBS spec. Doing so would adhere to existing interfaces that already work with / plug into APIs such as WebKMS without the need to invent a new interface.

Implementation experience and compatibility with other key formats suggests that the secret key should be the serialized SK value (instead of just being the seed as it is with Ed25519). This is slightly less safe than always producing a hashed scalar from the seed, but increasing interoperability is preferred.

This should be changed to be the new (and default) behavior and a major release made.

See: https://github.com/decentralized-identity/bbs-signature/tree/main/tooling/fixtures/fixture_data

Generators can be cached per count and api_id to improve performance.