BBS+ cryptographic algorithm in DID following: https://www.w3.org/TR/vc-di-bbs/

[Vytek]

Is your feature request related to a problem? Please describe.
Your implementation is really interesting however it does not contemplate the possibility of using the BBS+ algorithm used to decide what information to share and what not in full compliance with the GDPR or other regulations associated with SSI

Describe the solution you'd like
Introduction of the BBS+ proof algorithm according to https://www.w3.org/TR/vc-di-bbs/ using eg: https://github.com/suutaku/go-bbs

Describe alternatives you've considered
ZKP like: https://ieeexplore.ieee.org/document/10105959

Additional context
Using other cryptographic algorithm similar to ZKP like: https://github.com/consensys/gnark

[ehanoc]

Is your feature request related to a problem? Please describe. Your implementation is really interesting however it does not contemplate the possibility of using the BBS+ algorithm used to decide what information to share and what not in full compliance with the GDPR or other regulations associated with SSI

Describe the solution you'd like Introduction of the BBS+ proof algorithm according to https://www.w3.org/TR/vc-di-bbs/ using eg: https://github.com/suutaku/go-bbs

Describe alternatives you've considered ZKP like: https://ieeexplore.ieee.org/document/10105959

Additional context Using other cryptographic algorithm similar to ZKP like: https://github.com/consensys/gnark

This is not prescriptive; most keys used will be Ed25519 as in the Algorand protocol. Although wallets can have other capabilities in their KMS'es and assign other type of keys to their DID's authentication, endpoints, etc