Where quantum actually fits
The base layer is deliberately conventional: NIST-standardized post-quantum signatures (ML-DSA/Dilithium), hash-chained events, keys in Vault, KMS, or HSM custody, and local verification through versioned profiles. That layer carries most workflows on its own and is the subject of the assurance brief. None of it requires quantum hardware.
Hardware-conditioned provenance enters above that layer, as the optional top assurance tier. FieldHash Ledger uses hardware-executed measurement distributions as the verification signal for a Quantum Physical Unclonable Function, or Q-PUF: distributions shaped by backend state, calibration, gate behavior, and noise characteristics, producing device-conditioned fingerprints evaluated under disclosed hardware, parameter, and operating conditions. This is a conditioned evidence signal, not proof of physical unclonability across untested hardware. Where hardware is not used, simulation fallback is supported and labeled as a lower-trust tier, never passed off as the real thing.
Physical anchor
Quantum measurements add a hardware-conditioned signal to otherwise algorithmic provenance workflows.
Composed defense
Production verification combines statistical policy gates with integrity signatures and profile controls.
Backend agnostic
Users do not need their own quantum computer; FieldHash Ledger can call available provider APIs today.
PQC is the signing layer. Hardware-conditioned provenance is an additive evidence layer above it for long-retention or disputed-evidence workflows. It does not replace PQC.
What FieldHash Ledger does
FieldHash Ledger turns important digital artifacts into offline-verifiable evidence packages. Each certificate binds content hashes, quantum measurement statistics, backend metadata, policy profile, and cryptographic signatures into a portable trust object.
Hash
Bind the artifact with SHA-256/SHA-512 content digests.
Execute
Run a parameterized circuit through simulation or available QPU backends.
Fingerprint
Capture measurement distributions, noise statistics, and distribution digests.
Sign
Bind the evidence package with modern signatures, including post-quantum options.
Verify
Validate the certificate later through versioned standard, hardened, strict, or offline profiles.
Evidence, not assertion
The public evidence package documents real hardware execution, adversarial synthesis benchmarks, adaptive spoofing tests, cost data, and reproducibility materials. The claim boundary is explicit: FieldHash Ledger does not claim asymptotic runtime speedup at current scale. It claims security-oriented quantum utility.
Next phase
The hardware-conditioned tier is ready for independent validation and carefully scoped pilots. The next work is not to broaden the claim; it is to harden the proof, expand backend conditions, and quantify impact in real document ecosystems.
The goal is practical: stronger digital trust now, using quantum hardware as a measured evidence source rather than waiting for a fault-tolerant future.
Read the advanced proof package
For qualified technical review, the evidence package includes the preprint, adversarial results, hardware reports, manifests, and reproducibility materials.