Credo 1.0 roadmap

[TimoGlastra]

Opening this so we can discuss what it would entail to reach an 1.0 version of Credo.

I have some ideas on it but would love input.

My wishlist would include:

• move away from askar for storage. Find custom solution for sensitive data that needs to be encrypted
• default caching implementation with redis, so we can rely on cache more heavily.
• clean up of some older DIDComm features and protocols (v1 protocols, legacy did sov prefix, unqualified anoncreds identifiers)
• extract DIDComm out of core into separate package
• DIDComm v2 support
• stable version of OID4VC/OID4VP (although we don't have control over this)
• reworked crypto/wallet api, with support for Hardware Security Module.
• new APIs for handling verification / trust / revocation / status management. Also look at unifying different credential format APIs
• Fix the JSON-LD dependencies and have better support for caching
• Better support to work with non-self-signed X509 certificates
• control over which features are allowed (did methods, x509, credential formats, etc..)
• Security audit
• proper hosting/management of revocation status lists. Allow pluggable cloud storage interface

I think a lot could also be done after an 1.0 release. However i think mostly the security related features are important for an 1.0 release.