Skip to content

Public verification

Re-verify a Lab proof receipt

Qtonic Quantum Corp publishes signed Lab proof bundles. Anyone can re-check counts and signature metadata without trusting marketing copy. This page is the operator-facing procedure for that re-check.

Endpoints

Copyable verification commands

curl -sS https://qtonicquantum.com/api/lab/health | jq '.coverage.certifiedTotal,.proof'
curl -sS https://qtonicquantum.com/api/lab/coverage | jq '.certifiedTotal,.source,.proof'
curl -sS https://qtonicquantum.com/api/lab/proof/latest | jq '.snapshotId,.verification'

counts the public registry entries that hold the strict-verified tier; each one is traceable to its signed snapshot.

Verify the QShield by Qtonic Quantum Corp. observation record

The QShield by Qtonic Quantum Corp. observation record lists every observation with its SHA-256; its first and latest observations are signed with OpenSSH (Ed25519, namespace qshield-live-json). The public key is published at /.well-known/qshield-allowed-signers. Download the record from /proof-center/qshield-endurance/signed-record. Run these four commands; for the latest entry use .last in place of .first. Use jq -j, not jq -r: the signature covers the payload bytes exactly, with no trailing newline. The record's own verify note names the key file allowed_signers; it is the same file, saved here as qshield-allowed-signers.

curl -sS -o qshield-allowed-signers https://qtonicquantum.com/.well-known/qshield-allowed-signers
curl -sS -o signed-record.json https://qtonicquantum.com/proof-center/qshield-endurance/signed-record
jq -j '.first.payload' signed-record.json > sample.json && jq -j '.first.signature' signed-record.json > sample.sig
ssh-keygen -Y verify -f qshield-allowed-signers -I qshield-build@qtonicquantum.com -n qshield-live-json -s sample.sig < sample.json

Expected output: Good "qshield-live-json" signature for qshield-build@qtonicquantum.com with ED25519 key SHA256:8ZycHVUfjLI1R6RSIvlFaveDpVD5KS4jnQOaDXL7ScY, and the command exits 0. Any changed byte in either file makes it fail. A valid signature shows who signed that entry and that it is unchanged; it does not by itself establish running nodes or delivered traffic.

Scope

This procedure verifies surfaces published by Qtonic Quantum Corp and their signed proof metadata. Engagement artifacts remain operator-scoped.