The Architecture of Digital Trust.

Privacy-preserving verification and quantum-ready cryptographic infrastructure for the next generation of onchain finance.

Public: chains and verifiersProtocolPrivate: deviceidentity secretcredential openingMerkle pathTreerootNoir circuiteligibilityProof, 8,768 bytesroot, nullifier, scopeverifyProof on-chain

Public: chains and verifiers

Three layers, and what may cross them.

Private

The holder’s device

  • identity secret
  • credential claims and salts
  • Merkle path
  • Ed25519 keys (non-extractable)

Crosses outwarda proof, a signature, a presentation of chosen claims

Protocol

QuantLayer services

  • Poseidon commitment trees
  • ML-DSA and ML-KEM keys in custody
  • versioned policies
  • signed status lists

Crosses outwardroots, decisions, attestations

Public

Arbitrum and Robinhood Chain

  • published roots
  • spent nullifiers
  • key versions
  • verification results

Crosses outwardnothing further: this is the record

A verifier learns the statement, not the witness.

Six Noir circuits prove facts about credentials held in Poseidon commitment trees. The proof is 8,768 bytes and verifies on-chain for about 2.66 million gas.

Private witnessnullifierSecrettrapdoorattributesaltissuedAt, expiresAtpath: 20 siblingsleaf indexProver onlyNoir circuitleaf is in the tree rootissuedAt ≤ now < expiresAtattribute ≥ thresholdnullifier for this scopeeligibility v1BoundaryProofUltraHonk-BN2548,768 bytesPublic inputscontextrootissuercredentialTypenowthresholdscopenullifier
The verifier learns
that the holder is in the issuer’s tree, that the credential is current, that a hidden value clears a threshold, and a nullifier that makes the claim usable once per scope.
The verifier never receives
the identity secret, the attribute, the salt, the leaf position or the path. QuantLayer proves facts about credentials; it does not make transactions private.
How the privacy layer works

FIPS 203, 204 and 205, implemented in Rust.

ML-DSA and SLH-DSA sign; ML-KEM establishes keys. Ethereum accounts remain ECDSA and are not quantum-resistant, so on-chain post-quantum checks are attested by a quorum.

Sizes are fixed by the standards. Timings: medians on an Apple M2, Rust release build, measured in this repository (docs/pqc/BENCHMARKS.md).
AlgorithmStandardNIST categoryPublic keySignatureSignVerify
ML-DSA-44FIPS 20421,312 B2,420 B112 µs31 µs
ML-DSA-65FIPS 20431,952 B3,309 B156 µs46 µs
ML-DSA-87FIPS 20452,592 B4,627 B192 µs70 µs
SLH-DSA-SHA2-128sFIPS 205132 B7,856 B877 ms742 µs
SLH-DSA-SHA2-128fFIPS 205132 B17,088 B39 ms2.2 ms
SLH-DSA-SHA2-256sFIPS 205564 B29,792 B1,323 ms1.6 ms
How post-quantum keys work

An identifier that proves its own origin.

A did:quantlayer is derived from its inception key and a single-use challenge. Keys rotate, including from Ed25519 to ML-DSA-65, without changing the identifier.

Identity lifecycle

did:quantlayer:base32(
  SHA-256(algorithm, public key, nonce)
)

  1. pendingcreated, awaiting activation
  2. activekeys sign operations
  3. rotatednew version, same DID
  4. deactivatedterminal

Policies decide; nine steps prove it.

policy, version 3
{
  "id": "treasury.transfer",
  "version": 3,
  "mode": "hybrid",
  "hybrid": { "schemes": ["Ed25519+ML-DSA-65"] },
  "binding": {
    "chainIds": ["42161"],
    "appDomains": ["treasury.example.com"],
    "actions": ["treasury.*"]
  },
  "limits": { "maxLifetimeSeconds": 300 }
}
  1. 01requestWell-formed, canonical, a known version
  2. 02evidenceEvidence present and well-formed for the mode
  3. 03policyPolicy version exists, is active, not retired
  4. 04bindingChain, contract, app domain and action allowed
  5. 05timeNot yet expired, lifetime within the policy limit
  6. 06revocationKey versions and the request id not revoked
  7. 07subjectIdentity active, keys belong to it, purpose matches
  8. 08verificationEvery signature, credential or proof verifies
  9. 09replayNonce unused for this subject and domain

Every decision returns its reason code and the trace of these steps. A replayed nonce is denied.

Seven contracts, one verifier per circuit.

Solidity 0.8.28, role-separated access control, every address fingerprinted against its build before the SDK will call it.

Protocol architecture
QuantLayerAuthorizationManagerclassical, post-quantum, hybrid, credential, ZKQuantLayerProofVerifierUltraHonkVerifierAdapter6 circuit verifiersQuantLayerPqcAttestationVerifierEIP-712 PqcAttestationk-of-n attestorsQuantLayerCredentialRegistryissuers, roots, statusQuantLayerNullifierRegistryspent nullifiers, contextsQuantLayerIdentityRegistrydid:quantlayer, controllersQuantLayerKeyRegistrykey versions, algorithms

Arbitrum first, Robinhood Chain beside it.

NetworkChain IDEnvironmentExplorer
Arbitrum OnePrimary network42161Mainnetarbiscan.io
Arbitrum SepoliaPrimary network421614Testnetsepolia.arbiscan.io
Robinhood ChainSecondary network4663Mainnetrobinhoodchain.blockscout.com
Robinhood Chain TestnetSecondary network46630Testnetexplorer.testnet.chain.robinhood.com

One client, ten modules.

@quantlayer-protocol/sdk runs the same protocol code the API verifies: ESM and CommonJS, browser-safe, typed contract calls.

shell
npm install @quantlayer-protocol/sdk
identity.ts
import { createQuantLayerClient, generateEd25519Signer } from '@quantlayer-protocol/sdk';

const quantlayer = createQuantLayerClient({
  api: {
    baseUrl: 'https://api.quantlayer.example',
    apiKey: process.env.QUANTLAYER_API_KEY,
  },
});

// The DID is derived locally from the key and a single-use challenge.
const { signer } = generateEd25519Signer('k1');
const { did } = await quantlayer.identity.create({ signer });

Four rules the code enforces.

  1. 1

    Keys stay with their owner

    No private key is accepted, stored or logged by a QuantLayer backend. Custody keys never leave the Rust module unsealed.

  2. 2

    One signature, one operation

    Every signed authorization is bound to one action, one subject, one service and one short-lived nonce.

  3. 3

    Fail closed

    Unknown algorithms, missing evidence and incompatible protocol versions are refusals, never fallbacks.

  4. 4

    Say the trust assumption

    Post-quantum verification on-chain is attested by a quorum, not trustless. Every result names its assurance.

Read the protocol first.