PQAS
Post-Quantum Attestation Service
An independent cryptographic integrity layer, designed to prove a record existed at a known point in time, and remained unchanged since.
How PQAS Is Designed to Work
Five steps. Nothing is designed to leave the client. Everything anchors to a public post-quantum blockchain.
Client Document
The source document is designed to stay on the client's own infrastructure at every step. Nothing is uploaded to QF.
Local Hash
A cryptographic hash (SHA-256 or SHA-3) is taken client or server side. Only the hash ever leaves the source system.
Post-Quantum Signature
The hash is designed to be signed using ML-DSA (FIPS 204) or SLH-DSA (FIPS 205) — algorithms built to resist quantum attack.
Anchor to Chain
The signed record is designed to settle to a public post-quantum blockchain, giving it a permanent, independent timestamp.
Independent Verification
An auditor is designed to be able to query the chain directly — verification doesn't depend on QF or the original issuer still existing.
Design Principles
Sovereign by Design
Suitable for regulated and highly sensitive workflows, since sensitive documents never leave client infrastructure.
Provider-Agnostic
The API is designed to talk to an anchor provider, so the underlying chain can evolve without changing the client integration.
Permanently Auditable
Verification queries are designed to be public and permanent, so proof of integrity outlasts any single vendor relationship.