Signed-off-by: Victor Anene <firstname.lastname@example.org>
|19 hours ago|
|demo||19 hours ago|
|packages||19 hours ago|
|tests||20 hours ago|
|yarn.lock||19 hours ago|
Features | Getting started | Contributing | License
- 🏃 Runs in React Native & Node.JS
- 🔒 DIDComm v1 support
- 🌎 Aries Interop Profile v1 & v2 support
- With support for Chat, Mediator Coordination, Indy Credentials & and JSON-LD Credentials sub-targets
did:peer, with pluggable interface for registering custom did methods.
- OpenID for Verifiable Credential Issuance (only receiving JSON-LD credentials for now)
- 💡 Smart Auto Acceptance of Connections, Credentials and Proofs
- 🏢 Multi tenant module for managing multiple tenants under a single agent.
To get to know the AFJ flow, we built a demo to walk through it yourself together with agents Alice and Faber.
Divergence from Aries RFCs
||Properties that are not recognized should be ignored, meaning this shouldn't limit interoperability between agents. As the image url is self-attested it could give a false sense of trust. Better, credential based, method for visually identifying an entity are not present yet.||Even though not documented, almost all agents support this feature. Not including this feature means AFJ is lacking in features in comparison to other implementations.|
|Revocation Notification v1 uses a different
If you would like to contribute to the framework, please read the Framework Developers README and the CONTRIBUTING guidelines. These documents will provide more information to get you started!