This repository is a production-grade, cross-platform mobile wallet for self-sovereign identity (SSI), built with React Native and the Credo-ts agent framework. It supports multiple verifiable credential formats (AnonCreds, W3C VC, SD-JWT, mdoc) and protocols (DIDComm v1, OpenID4VCI, OpenID4VP, ISO 18013-7). The wallet handles the full credential lifecycle: issuance, storage, presentation, refresh, and revocation. It also includes a verifier subsystem for generating and processing proof requests, and an Overlay Capture Architecture (OCA) layer for branded credential display. The architecture is a monorepo managed by Yarn 4, with packages for core UI (`@bifold/core`), credential display formatting (`@bifold/oca`), proof request handling (`@bifold/verifier`), React hooks for agent state (`@bifold/react-hooks`), remote logging (`@bifold/remote-logs`), and platform attestation (`react-native-attestation`, `expo-attestation`). Dependency injection via tsyringe is central, with a large token catalog (`TOKENS`) enabling component and service overrides. The sample app (`samples/app`) demonstrates full integration with Android and iOS native builds. Key entry points include `packages/core/src/App.tsx` (root component), `packages/core/src/container-impl.ts` (DI container setup), and the navigator stacks (`RootStack`, `TabStack`, `OnboardingStack`). Data flows are driven by Credo-ts agent events and OpenID4VC credential metadata, with a background refresh orchestrator that verifies credential status and triggers re-issuance. External dependencies include Credo-ts, Indy VDR, Askar, React Native, and various native modules for biometrics, keychain, and camera. The codebase demonstrates strong engineering practices: comprehensive unit and snapshot tests, localization (en, fr, pt-BR), theming, accessibility, and a modular package structure. However, there are maintenance risks from patched dependencies, legacy OCA code paths, and snapshot brittleness. Overall, it is a well-crafted, reusable foundation for any SSI wallet project.
ACA-Py is a production-ready, open-source Self-Sovereign Identity (SSI) agent that implements the Hyperledger Aries ecosystem. It acts as a server-side agent for issuers, holders, and verifiers of decentralized digital credentials. The system supports multiple verifiable credential formats including AnonCreds (CL signatures), W3C Verifiable Credentials with Linked Data Proofs (Ed25519, BBS+, ECDSA secp256r1), and SD-JWT. It implements DIDComm v1 and v2 messaging protocols for secure peer-to-peer communication, along with a comprehensive set of Aries protocols for credential issuance, presentation, DID exchange, mediation, routing, and revocation. The architecture is built as a modular Python application using aiohttp for HTTP/WebSocket transport. It follows a controller pattern where external business logic interacts via a REST API and receives asynchronous webhook notifications. Core components include a dependency injection system (InjectionContext), an event bus for internal pub/sub, a plugin registry for extensibility, protocol-specific handlers for each DIDComm message type, a wallet abstraction layer supporting multiple backends (Askar, Kanon, Indy), a database manager with SQLite and PostgreSQL backends, and a DID resolver framework supporting multiple DID methods (did:key, did:indy, did:web, did:peer, did:webvh). The agent is configured via YAML files, environment variables, or CLI arguments. Key entry points include the 'aca-py' CLI command (start, provision, upgrade) and the admin REST API. The server listens for DIDComm messages over HTTP and WebSocket, processes them through protocol handlers, and persists state in the configured database. External systems interact via the admin API for credential management, DID operations, and configuration. The agent supports multi-tenant deployments with wallet isolation, mediation/routing for scalability, and integration with Indy ledgers for schema and credential definition registration. External dependencies include native cryptographic libraries: aries-askar for secure storage, anoncreds for anonymous credentials, indy-credx for Indy credential exchange, indy-vdr for Indy ledger interaction, and ursa-bbs-signatures for BBS+ signatures. It also depends on didcomm-messaging for DIDComm v2 support, pyld for JSON-LD processing, and psycopg for PostgreSQL connectivity. The project is maintained by the OpenWallet Foundation and follows an LTS release model with active community contributions.