Identifiers that verify their own inception.
A did:quantlayer is the base32 SHA-256 of its first key, its algorithm and a single-use challenge nonce. Anyone can check that an identifier was created with the key it names, and nobody can squat one.
Identity registration
Every change is authorised by a signature over a single-use challenge: one action, one subject, one service, once, for a short time.
- Challenge
- POST /v1/identities/challenges returns a nonce, an audience and an expiry for one named action.
- Statement
- The client signs “QUANTLAYER-SIG-V1:identity-authorization” followed by the canonical JSON of the statement.
- Proof of possession
- A new key signs the same statement, so a key cannot be registered by someone who does not hold it. Post-quantum proofs are verified in Rust.
- Derivation check
- The SDK derives the DID locally and refuses a server answer that differs.
Lifecycle states
- pending
- active
- suspended
- deactivated
Key lifecycle
Register, rotate across algorithms, revoke. Historic signatures keep verifying after rotation and stop after revocation.
Wallet ownership verification
- Account linking
- An EVM account (CAIP-10) is linked only when the identity key authorises it and the account signs the same statement as EIP-712 typed data.
- Smart accounts
- EIP-1271 contract signatures are supported through an on-chain check.
- Uniqueness
- An account can be actively linked to at most one identity, enforced atomically in the database.
- Sign-in
- The developer console signs in with an EIP-712 challenge; the session is held in an httpOnly cookie.
Credentials and selective disclosure
Issuers are identities with post-quantum custody keys. Holders accept credentials only after checking them locally.