Keyring
Identity Toolkit / Platform
Community
Details
License Open source — Apache-2.0 (keyring-wallet and keyring-bifold)
Dev Status 🔬 Beta
Dev Status Detail Beta (the project's own label: 'not ready for production use'; available only as a test build, with no public store listing; commits continue daily)
Owner Harvard's Berkman Klein Center (Applied Social Media Lab) and the Applied Technology Lab at the Harvard John A. Paulson School of Engineering and Applied Sciences; the GitHub organization is 'berkmancenter'. No legal entity beyond these labs is stated
Governing Body None stated beyond the maintainers (the contributing guide says the maintainers read everything and decide; over-the-air updates each need a maintainer's approval)
Country Not stated by the project.
Stack React Native 0.81 and TypeScript on Node.js 20; Credo-TS agent framework (AnonCreds, Indy VDR); Askar for TSP keys and envelopes; Yarn 4, Appium end-to-end tests; a Node.js witness service with a web UI and REST API
Funding Not stated by the project.
Last Investigated Nov 12, 2026
Identity Toolkit / Platform Attributes
Origins Built at the Applied Social Media Lab of Harvard's Berkman Klein Center, continuing at the Applied Technology Lab at Harvard SEAS; it started from the BC Wallet mobile app and forks Bifold, extending it for relationship credentials among communities
Database On-device wallet storage through Askar (the Credo-TS/Bifold storage layer); a community's identity keys are held by a server-side agent
Query Language N/A: wallet app; no query language
Data Formats W3C Verifiable Credentials 2.0 with Data Integrity proofs for relationship credentials; AnonCreds inherited from Bifold; JSON messages over DIDComm v2 or TSP
Mobile Support Yes: iOS and Android (React Native)
Web Support
Native Apps Yes: iOS and Android apps, distributed only as test builds; no public store listing
Terms Apache-2.0 (open source); commits must be signed and carry a DCO sign-off
Funds
Based On OpenWallet Foundation Bifold Wallet (forked), BC Wallet Mobile (where the app started), Credo-TS; Trust Spanning Protocol, DIDComm v2, W3C Verifiable Credentials 2.0
Permissions Open source — Apache-2.0; commits must be signed and DCO sign-off is required
Development Tools yarn quickstart and demo scripts, a local mediator, Appium end-to-end tests, a 'Building your own use case' guide, and the vrc-reference and react-native-attestation packages
Authentication & Identity The wallet is locked by a PIN, with biometrics if the person wants them; agent approvals add a step-up check; relationship credentials are issued between people's wallets
Storage Model Local-first: keys and credentials stay on the phone; community identities are held by a server-side agent
Interoperability Medium: W3C VC 2.0, DIDComm v2, Trust Spanning Protocol, AnonCreds; works with the OpenVTC / First Person Project stack (VTA, VTC, mediator); KERI credentials are listed as planned
Data Portability
Governance & Decision Making Maintainer-led: issues and pull requests are welcome, the maintainers decide, and over-the-air updates each need a maintainer's approval
Identity Standards W3C Verifiable Credentials 2.0 (Data Integrity proofs); DIDComm v2; Trust Spanning Protocol; AnonCreds; the Decentralized Trust Graph credential specification and Trust Tasks from Trust Over IP and LF Decentralized Trust
Identity Standards - List
DID Methods Supported Relationship DIDs are used; no DID method is named in the repositories. Reported to the DTG Interop Board as did:peer, did:key and did:webvh
DID Methods Supported - List
Key Management Keys stay on the phone; optional hardware-backed signing with a key in the Secure Enclave (iOS) or StrongBox (Android) after a biometric or passcode check
Credential Types Verifiable Relationship Credentials (VRCs) between people, Verifiable Witness Credentials (VWCs), community cards; AnonCreds from Bifold; KERI credentials planned
Credential Types - List
Verification Method Credential signatures checked in the wallet; witnessed credential exchange through a witness service that, per its README, never sees private data; optional biometric hardware attestation
Privacy Features Notifications carry no message content; disappearing messages per chat; a vetter can vouch without being named; the witness service never sees private data
Authentication Methods PIN with optional biometrics; step-up check for agent approvals
Revocation Mechanism
Agent Types Supported People, communities and agents: a server-side agent holds a community's identity keys, and the wallet approves agent actions with a step-up check
Wallet/Client Types Mobile wallet for iOS and Android
Recovery Mechanisms
Compliance / Regulations
Credential Exchange Protocols Trust Spanning Protocol or DIDComm v2, chosen per peer (DIDComm with contacts); one-to-one end-to-end encrypted chat . Reported to the DTG Interop Board as also using MLS rooms for communities
Credential Exchange Protocols - List
Trust Framework Verifiable Trust Community (VTC) model from the Decentralized Trust Graph work; no accredited trust framework is stated
Cost Model
Censorship Resistance Not stated by the project; keys and credentials are held on the person's phone
Relationships
How this tool connects to other tools and organizations, from relationships reviewed by the OpenHaven data steward. They describe how projects connect, not how good they are.
- Speaks protocol
- Interoperates with