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

  1. pendingCreated with proof of possession; awaiting operator activation.
  2. activeIts keys may authorise operations and sign presentations.
  3. suspendedTemporarily blocked by an operator; reinstatable.
  4. deactivatedTerminal. The identifier is never reused.

Key lifecycle

Register, rotate across algorithms, revoke. Historic signatures keep verifying after rotation and stop after revocation.
k1, version 1history still verifiesEd25519status: retiredk1, version 2signs new requestsML-DSA-65status: activerotate-key, single-use challengeTransition statementauthorised by version 1possession proven by version 2The algorithm may change on rotation: classical to post-quantum

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.
Issuersigns the documentkeeps no claim valuesML-DSA-65 in custodyclaim digestssubject commitmentstatus list entryHolderaccepts after checkingsignature, binding, digestsclaims, saltsreveal: level, countryVerifiersees revealed claims onlyissuer signaturestatus listholder bindingaudience, noncequantlayer.credential/2A presentation is bound to one audience and one nonce:replaying it to another verifier fails.

Stated limits