Provenance System

FieldHash

Quantum-anchored, offline-verifiable provenance for long-retention digital records. FieldHash combines post-quantum signatures with optional hardware-executed quantum fingerprints to make trade records, compliance evidence, and other high-integrity artifacts harder to forge across time and across organizations.

The Threat Model

Harvest Now, Decrypt Later. Adversaries are capturing encrypted data today, waiting for quantum computers to break current cryptography. When that happens, archived trade records, audit trails, compliance packages, and long-retention evidence become exposed.

This is not limited to AI. Trade documentation, compliance records, investigation files, and long-retention institutional evidence all need to remain tamper-evident for years, sometimes in degraded or offline verification environments.

Current RSA and ECC signatures have an expiration date. We just don't know exactly when.

The Solution

FieldHash provides offline-verifiable evidence for long-horizon data integrity by combining modern post-quantum cryptography with optional quantum hardware anchoring. It is backend-agnostic and can use available provider APIs now.

Post-Quantum Signatures

NIST ML-DSA (Dilithium)—standardized, battle-tested, quantum-resistant. Optional ML-KEM (Kyber) for encrypted attachments.

Content Binding

SHA-256 (primary) and SHA-512 (audit trail) for cryptographic content binding. Every protected artifact is immutably linked to its evidence.

Optional Quantum Hardware Anchoring

When IBM Quantum or Quantum Inspire hardware is available, FieldHash captures device-conditioned fingerprints and noise statistics. Users do not need to own a quantum computer; the system can call available backends through provider APIs.

Simulation by Default

Full cryptographic security without specialized hardware. Simulation mode covers many near-term workflows, while hardware-backed profiles add an extra physical provenance layer when higher assurance is required.

HSM/Vault Integration

Private keys never leave secure custody. Zero egress to application memory. Non-exportable signing keys in Vault, KMS, or HSM.

Measured Evidence

FieldHash is not a concept-only security claim. It has been executed on real quantum hardware with reproducible evidence and adversarial validation.

Hardware Backends

Executed on IBM Quantum and Quantum Inspire with auditable job records.

Baseline Finding

A standard-profile uniform-blend attack passed in 15/800 trials (1.875%).

Hardened Closure

The hardened profile closed that measured gap to 0/800 under the same attack family.

Adaptive Result

Production-gated adaptive testing produced 0/5000 successful forgeries per tested model.

The public evidence package includes the preprint, execution reports, adversarial benchmarks, and reproducibility materials.

The Workflow

Five steps from content to verifiable evidence:

1

Hash

Content bound with SHA-256/SHA-512

2

Execute

Parameterized circuit run on simulation or available QPU backends via API

3

Fingerprint

Distribution digest and noise statistics captured

4

Sign

Evidence package signed via HSM using ML-DSA

5

Verify

Offline verification using versioned trust profiles

Verification Model

Fully offline-capable. No network required for verification. Evidence packages are self-contained and can be validated in air-gapped environments.

Trust Tiers

Strict— Highest-assurance hardware-backed verification
Hardened— Tightened hardware profile validated against measured spoofing
Standard— Simulation-based (default)
Offline— Air-gapped optimized

Production deployments use composed verification: statistical policy gates plus signature-bound integrity metadata. Profiles are versioned for forward compatibility.

Security Architecture

Client mTLS and JWT authentication
Least-privilege RBAC and tenant isolation
Rate limiting (100 req/min)
PII-aware logging with redaction policies
Non-exportable signing keys in HSM/Vault

Every protected artifact generated by Lumenais is FieldHash-signed. Every hypothesis, every discovery, every self-modification—cryptographically bound to its evidence.

Learn More

Review the public evidence package first, then the deeper technical specification for protocol details, security assumptions, and integration guides: