How the system is built, layer by layer.
A TypeScript protocol kernel, a Rust post-quantum module, Noir circuits, Solidity contracts and a NestJS backend, each with its own tests and each reachable from one SDK.
Protocol architecture
Domain packages with enforced layering: shared, core, crypto, then identity, credentials, privacy, ZK, authorization, networks. The SDK bundles them.
Cryptographic architecture
- Classical
- Ed25519, secp256k1, SHA-256, Keccak-256 and Poseidon-BN254 through the audited @noble libraries. Verification only: the backend has no signing function to misuse.
- Post-quantum
- ML-KEM (libcrux, formally verified), ML-DSA (libcrux) and SLH-DSA (fips205), in Rust, cross-checked against an independent JavaScript implementation and NIST vectors.
- Zero-knowledge
- Six Noir circuits compiled to 2^16-gate UltraHonk circuits; proofs of 8,768 bytes; artifacts and Solidity verifiers are reproducible in CI.
- Encodings
- Canonical JSON with signing-purpose prefixes (QUANTLAYER-SIG-V1), versioned codecs, and domain tags for every hash.
Smart contract architecture
Solidity 0.8.28 on the Cancun EVM. Roles are separated: issuer administration, circuit administration, attestor management and pausing are distinct.
- Proof verification
- QuantLayerProofVerifier.verifyProof costs 2.63 to 2.66 million gas, including binding checks and consuming the nullifier.
- Versioning
- Each circuit records its proof system and verification-key hash; a new circuit version is a new registration.
- Fingerprints
- Deployed bytecode is identified by keccak256 with immutables masked; the SDK refuses an address whose code does not match.
Backend architecture
- Roles
- One codebase, three roles: the HTTP API, background proof workers (BullMQ on Redis) and the chain indexer.
- Storage
- PostgreSQL in three schemas: meta (public projections), vault (sealed keys), sensitive (encrypted aggregates, AES-256-GCM with per-row associated data).
- Credentials
- Project API keys with scopes; the secret is shown once and kept only as an HMAC verifier under a KEK-derived key. Wallet sessions manage projects and keys.
- Interface
- OpenAPI 3.1, structured errors with request ids, rate limits, OpenTelemetry tracing.
Cross-chain integration
A credential issued on one chain can be checked on another. Every result names its evidence kind and the assurance it rests on.
| Network | Chain ID | Environment | Explorer | Public RPC | QuantLayer contracts |
|---|---|---|---|---|---|
| Arbitrum One | 42161 | Mainnet | arbiscan.io | https://arb1.arbitrum.io/rpc | Not deployed |
| Arbitrum Sepolia | 421614 | Testnet | sepolia.arbiscan.io | https://sepolia-rollup.arbitrum.io/rpc | Deployed |
| Robinhood Chain | 4663 | Mainnet | robinhoodchain.blockscout.com | https://rpc.mainnet.chain.robinhood.com | Not deployed |
| Robinhood Chain Testnet | 46630 | Testnet | explorer.testnet.chain.robinhood.com | https://rpc.testnet.chain.robinhood.com | Not deployed |