The framework has gained a lot of momentum lately. The community has been growing quickly with various governments and organizations stepping in. Our current contributor count is 37, and the working group calls now have around 10 active participants (as opposed to the two we had two years ago). The potential of the framework has become clear to developers other than us (the fanatics). For example, at Animo we recently received funding from the EU NGI eSSIF-Lab initiative to lift the framework to the next level regarding mobile development options.
- Full support for the out of band and did-exchange protocols
- Postgres wallet support
- Previously the framework only supported SQLite. This addition ensures the framework is better suited for cloud infrastructure.
- Wallet import/export support
- This addition enables users to migrate their wallet data to and from other Hyperledger Indy-based wallets.
- Pickup protocol v2 for better control over interactions with the mediator
- Support for the issue-credential-v2 protocol
- The issue credential and present proof v2 extend the framework with the ability to support multiple credential and proof formats. Instead of adding a separate API for the v2 protocols, we have put a lot of effort in designing a single, easy-to-use API that works with both versions and is extensible for later versions in the future. In the next release we’ll be adding support for the present proof v2 protocol.
- Credential revocation and revocation notifications for holders and verifiers
- This allows holders to prove that a credential hasn’t been revoked and verifiers to verify this. The revocation notifications allow the holders to be informed about the fact that one of their credentials has been revoked, rather than discovering this when trying to present proof.
- Full did:peer support
- A generic DID resolver that currently supports did:key, did:web, did:sov and did:peer.
- An upgrade assistant to help users update their wallets to newer versions of the framework
- As the framework evolves over time, some of the underlying data structures may change. With the upgrade assistant, we aim to make it as easy as possible for users to migrate.
We’re already working hard on version 0.3.0 that will, just like the 0.2.0 release, be packed with new features such as support for the W3C Verifiable Credential Format and BBS+ Signatures 2020, making the framework fully AIP 2.0 compliant.