aries-framework-go
aries-framework-go copied to clipboard
hyperledger-archives
Create new repo for `github.com/hyperledger/aries-framework-go/component/kmscrypto/crypto/primitive/bbs12381g2pub`
This proposal recommends splitting the `github.com/hyperledger/aries-framework-go/component/kmscrypto/crypto/primitive/bbs12381g2pub' package into a separate repo. Reasons that speak in favour of this change:
- ever since ursa was moved to EOL, assets such as the BBS+ implementation of ursa have been moved to their own repo.
- the BBS+ IETF standard draft has evolved past the current implementation in go after the recent work by Tessaro et al.. It would be good to have a dedicated package maintained by cryptographers within the Hyperledger project such as @adecaro and myself; the idea would be to strike a balance between compatibility with the existing assets and deployments and the new versions of the standard.
Thoughts?
I understand that aries-framework-go is targeted for archival, and propose to create a new sub-repository for BBS+ Go implementation, fully maintained and tracking updates to the standard. I'd be happy to act as one of the initial maintainers, along with any of the maintainers from
https://github.com/hyperledger/aries-framework-go/blob/main/MAINTAINERS.md
and @swcurran (Aries maintainer on TOC)
Any thoughts?
Sounds like a good idea. Where do you plan to put it? It could go in Aries (e.g. aries-bbssignatures-go), if you want. Or do you have another place it could go?
SGTM, I think in aries would be a good fit. @sudeshrshetty , @troyronda, @fqutishat - your thoughts?
@swcurran it looks like there are no strong opinions, so should we go for something like https://github.com/hyperledger/aries-bbs-go ?