Wallet identities
Chain-agnostic ownership with public accounts and isolated signing material.
Examples describe accepted contracts unless explicitly marked implemented. They do not imply a deployed API, SDK, signer, or production environment.
Registry boundary#
The implemented registry stores wallet identity, namespace, lifecycle, public account metadata, provisioning intent, and an opaque signer configuration reference. It has no plaintext key or signer-share column.
- Database-backed uniqueness
- Concurrency-safe first resolution
- Durable provisioning outbox
- No invented addresses before provisioning
Chain accounts#
A wallet identity may own several chain-family accounts. EVM secp256k1 and Solana Ed25519 are the initial adapters; neither key-generation adapter is implemented yet.
Wallet Identity
├── EVM account (secp256k1)
├── Solana account (Ed25519)
└── Future chain adaptersContinuity#
Recovery, export, ownership transfer, and migration remain available through dedicated continuity policies even when an entitlement downgrade restricts ordinary premium use.
Review the engineering-readiness snapshot for current service boundaries. Contact the team before integrating a capability that remains gated.