Infrastructure that keeps the witness private and the result public.
Four modules over one protocol kernel: canonical encodings, versioned codecs and a single error model, used identically by the SDK in the browser and the API on the server.
Architecture overview
What stays on the holder’s device, what the protocol keeps, and the one thing that crosses into public view.
Core modules
- Identitydid:quantlayer identifiers derived from their inception key; key registration, rotation and revocation; wallet linking with EIP-712.
- PrivacyPoseidon commitment trees, six Noir circuits, nullifiers, selectively disclosable credentials and signed status lists.
- Quantum securityML-DSA, SLH-DSA and ML-KEM in Rust; custody keys sealed under a key-encryption key; algorithm migration with signed transitions.
- AuthorizationVersioned policies evaluated in nine steps over classical, post-quantum, hybrid, credential and ZK evidence.
Protocol lifecycle
From an API key to a recorded result, in the order the platform runs it.
- 01RegisterAn integrator creates a project and a scoped API key with a wallet session.
- 02Establish identityA holder creates a did:quantlayer, signing a single-use challenge; an operator activates it.
- 03IssueAn issuer with an ML-DSA-65 custody key signs a quantlayer.credential/2 document. The issuer keeps no claim values.
- 04CommitThe credential’s leaf joins the issuer’s Poseidon tree; the root is published.
- 05Prove or presentThe holder proves a statement with a Noir circuit, or presents chosen claims bound to an audience and a nonce.
- 06DecideThe authorization engine evaluates the request against a versioned policy and returns a decision with its trace.
- 07RecordRoots, nullifiers, key versions and verification results are recorded on Arbitrum or Robinhood Chain.
Integration model
Three ways in; all of them run the same protocol code.
- TypeScript SDK
- @quantlayer-protocol/sdk: signing, presentations and proofs run locally; platform calls go to the API with a scoped key.
- HTTP API
- NestJS on Fastify with an OpenAPI 3.1 document. Project API keys carry scopes; wallet sessions manage projects and keys.
- Contracts
- Seven Solidity contracts; the SDK resolves addresses only from deployment records and checks their bytecode fingerprint.
Supported capabilities
- Signatures
- Ed25519, ES256K, ML-DSA-44/65/87, SLH-DSA-SHA2-128s/128f/256s
- Key encapsulation
- ML-KEM-512/768/1024
- Hybrid schemes
- Ed25519+ML-DSA-65, ES256K+ML-DSA-65
- Proof system
- UltraHonk over BN254 (Noir 1.0.0, Barretenberg 6.0.0)
- Circuits
- membership, credential-ownership, credential-validity, balance-threshold, nullifier-uniqueness, eligibility
- Networks
- Arbitrum One, Arbitrum Sepolia, Robinhood Chain, Robinhood Chain Testnet