A decision you can replay and audit.
Requests are built and signed by the client, then evaluated against an immutable, versioned policy. Every decision returns allow or deny, a reason code and the trace of each step.
Evidence modes
A policy names exactly one mode. The assurance column is what the on-chain manager reports for that mode.
| Mode | Evidence | On-chain assurance |
|---|---|---|
| classical | Ed25519 or ES256K signature by a registered key | Trustless on-chain (EIP-712 ECDSA) |
| post-quantum | ML-DSA or SLH-DSA signature, verified in Rust | Attested on-chain |
| hybrid | Classical and ML-DSA-65 over the same input; both must verify | Classical half on-chain, post-quantum half attested |
| credential | A quantlayer.credential/2 presentation with required claims | Status on-chain, presentation attested |
| zk-eligibility | An UltraHonk proof bound to the request digest | Trustless on-chain |
Policy evaluation
The engine runs these steps in order and stops at the first that fails.
- 01request
- 02evidence
- 03policy
- 04binding
- 05time
- 06revocation
- 07subject
- 08verification
- 09replay
Hybrid authorization
Policies
- Versioned and immutable
- Publishing creates a new version with a digest; a minimum version retires older ones.
- Binding
- Chain ids, contracts, app domains and action patterns the request must match.
- Requirements
- Allowed classical schemes, post-quantum algorithms, hybrid schemes, credential issuers and claims, or a circuit with pinned public inputs.
- Key purpose
- The key must hold the purpose the policy names, for example authentication.
Expiration and replay protection
- Lifetime
- issuedAt and expiresAt in Unix seconds; the lifetime may not exceed the policy’s limit, with bounded clock skew.
- Nonce
- 32 random bytes, single-use per subject and domain. A replay is denied with NONCE_REPLAYED.
- Request id
- Unique per request; emergency revocation can cancel a request id before it is used.
- Digest
- The EIP-712 digest of the request equals the contract’s QuantLayerAuthorizationHash, so the same request is checked off-chain and on-chain.