Proof Center · QShield by Qtonic Quantum Corp.
Every check recorded. Every record verifiable.
Post-quantum protection between systems. Verify the completed three-day run and the signed record of the 50-location network yourself.
Completed endurance run · September 13–16, 2026
Three days. 4,107 checks. Zero failures.
Two Oregon hosts. 72 hours. Post-quantum key establishment, with no classical fallback. The record below is sealed.
Each mark is a recorded check. Longest interval: 64 seconds.
- Successful checks
- 4,107
- Failed checks
- 0
- Recorded ping loss
- 0
- Longest interval
- 64 s
QShield by Qtonic Quantum Corp. · location network
The location network.
Every observation dated; the first and latest signed.
Reading the location feed
Live observation appears after the next read of the location feed; the signed record of 28 Sep 2026 is shown until then.
Historical record, 28 Sep 2026. Bright marks: confirmed cities in that signed record. Larger marks: the five capital origins. Lines: logical connections between paired cities. Select a city to inspect it.
Historical record, 28 Sep 2026
482 observations over 50 hours, to · each lists all 50 cities and regions · latest signed
Qualifying soak: not started. Target: 10,000 elapsed hours from a qualifying signed start. Observed location-hours do not count toward this target.
Download the signed record → Signer key → SHA256:8ZycHVUfjLI1R6RSIvlFaveDpVD5KS4jnQOaDXL7ScY
- Cities and regions
- 50
- Observations
- 482
- Hours on record
- 50
How this network is selected
Inspect the location roster
Signed record: 2026-09-26 16:02 UTC to 2026-09-28 18:23 UTC, published about every six minutes.
What this evidence establishes
QShield by Qtonic Quantum Corp. / Verified connection
Oregon ↔ Stockholm
Last verified session · 17 Sep 2026 15:20 UTC
Approximate regional locations · logical connection
- Observed locations
- 2
- Probe replies
- 6 / 6
- Slowest round trip
- 155.2 ms
Oregon · Last verified session
Session: active · ML-KEM-1024 / ML-DSA-87 / TLS_AES_256_GCM_SHA384 · RTT: 155.2 ms
Observed:
Endpoint samples, taken every 60 seconds while observations are live. The completed endurance run is a separate, sealed record.
What these observations establish
The line is a logical connection between the two endpoints. Compare each live receipt’s build identity with the published hash.
“Information stolen today can remain valuable to an adversary for decades. Organizations need a practical way to begin protecting it now.”
How the completed run worked
What ran
For traffic inside its protected boundary, QShield by Qtonic Quantum Corp. uses ML-KEM-1024 instead of RSA or elliptic-curve key exchange to address harvest-now-decrypt-later exposure.
Two Linux hosts in separate Oregon availability zones. Each cycle checked connectivity, service status and 64 KiB data integrity, then paused 60 seconds.
If required security conditions cannot be held, protected traffic stops. There is no weaker fallback.
| Key establishment | ML-KEM-1024 (FIPS 203) |
|---|---|
| Endpoint authentication | ML-DSA-87 (FIPS 204) |
| Packet encryption | AES-256-GCM |
| Classical fallback | None |
| Pre-shared-key mode | Not negotiated. ML-KEM-1024 used for key establishment |
| Private keys | Held on the endpoints |
| Third-party key access | None, including Qtonic Quantum Corp |
| Hardware changes | None. Software only |
| Hosts | Two AWS Linux instances, separate Oregon availability zones |
| Start | 2026-09-13 04:28:48 UTC |
| End | 2026-09-16 04:29:04 UTC |
| Duration | 259,219 seconds on the run's monotonic clock; 259,216 seconds between the wall-clock start and end stamps |
Verify the evidence files
Check it yourself
Compare the downloaded files with the published SHA-256 hashes. Verification happens in your browser; files never leave your machine.
At harvest, both runtime executable paths matched the build below. Zero restarts were recorded.
QShield by Qtonic Quantum Corp. build SHA-256
b7be33990216997afe99b80090e36adf0add27ae90842a012712e265d32519e3Run log SHA-256
560d5f9cc5818483d32f9009acdf0471805e9d4f469052a2c1c93cc4838dd4b0Choose any file from the evidence bundle.
Command-line check:
sha256sum -c SHA256SUMS python3 verify_qshield_log.py client.jsonl
Evidence bundle
- Download
Everything in one file
All evidence below as a single zip
- Download
Run log
client.jsonl: all 4,107 checks, their timing and result
- Download
Terminal receipt
HARVEST.txt: final counts, elapsed time, process IDs, restarts and build hash
- Download
Server state receipt
D-state.txt: process, restart count, build hash and run configuration
- Download
Peer state receipt
E-state.txt: process, restart count and build hash
- Download
Verifier
verify_qshield_log.py: rerun every check on the log yourself
- Download
Verifier output
verify-output.txt: 11 of 11 checks confirmed
- Download
Manifest
SHA256SUMS: hash of every file in the bundle
Endurance results apply to the build identified in “Verify the evidence files.” The product is not represented as FIPS 140-3 validated or as holding Government authorization.
The first and latest entries of the observation record can be checked with the published key: signature verification recipe →
Bring one connection that matters.
Bring a confidential transfer or a link between locations. Your team and ours define the scope, key custody and success criteria for a guided evaluation.