For the complete documentation index, see llms.txt. This page is also available as Markdown.

Digital Wallet

The digital wallet is the user-controlled, on-device container for all identity assets and credentials. It uses public-private key cryptography and secure enclave storage to keep data tamper-proof.


Capabilities in this category

Identity wallet

Verifiable credentials

Selective disclosure


Identity wallet

A user-controlled digital wallet that stores all identity assets on-device.

What it does — Provides encrypted, on-device storage for identity documents, biometric assets, account credentials, and verifiable credentials. Each wallet is created with a unique decentralized identifier (DID) and a public-private key pair generated in the device's secure enclave.

When to use it — Foundational capability — every user has a wallet. Used implicitly by every other capability that stores identity data.

Key details

  • Public-private key cryptography (FIDO2-compatible)

  • Private key stored in device secure enclave

  • Decentralized identifier (DID) per wallet

  • Encrypted at rest with device-bound keys

  • Recoverable via 12-word mnemonic


Verifiable credentials

Issue, store, and present W3C-compliant verifiable credentials.

What it does — Acts as a verifiable credential holder and provider. Trusted issuers (employers, institutions, agencies) sign credentials and deliver them to the user's wallet. Users can present credentials to relying parties, who verify authenticity cryptographically without contacting 1Kosmos.

When to use it — Decentralized identity ecosystems, professional certification, employment verification, age verification, membership credentials, and any flow requiring tamper-proof identity assertions.

Key details

  • W3C Verifiable Credentials data model

  • Cryptographically signed by issuers

  • Selective disclosure supported (share only required attributes)

  • Verification possible without contacting 1Kosmos

  • Tamper-evident through digital signature


Selective disclosure

Share only the specific attributes a relying party needs.

What it does — When presenting a credential, users can disclose only the attributes required for the request — for example, proving "over 21" without revealing date of birth, or proving employment without revealing employer or salary.

When to use it — Privacy-respecting verification flows, age verification, eligibility checks, and compliance-driven minimum data exposure scenarios.

Key details

  • Built into the verifiable credential presentation flow

  • Cryptographic guarantees on disclosed and undisclosed fields

  • Consent prompt shown before any disclosure

  • No data leaves the device without explicit user approval

Wallet architecture

The wallet uses three layers of protection:

Layer
Mechanism
Purpose

Storage

Device secure enclave + encryption

Prevents tampering and unauthorized access

Cryptography

Public-private key pair (FIDO2)

Ensures only the user can sign and present

Recovery

12-word mnemonic phrase

Allows wallet to be restored on new devices

Last updated

Was this helpful?