6
real commercial quantum-cloud execution paths
QStrike · public integrity boundary
Governed quantum-cloud integrity without a direct encryption-break claim.
QStrike integrity boundary on the quantum-cloud runtime: a governed side-channel and ephemeral leak expose nonce information; no direct encryption-break.
4
physical modalities
Up to 8
represented access services
0
direct encryption-break claims
What the profile names mean
Vendor names identify the commercial services used by approved QStrike workloads. They do not imply customer runtime, a direct encryption break, or provider endorsement.
IBM Quantum
superconducting · quantum-cloud execution path
Rigetti
superconducting · quantum-cloud execution path
Quantinuum
trapped ion · quantum-cloud execution path
IonQ
trapped ion · quantum-cloud execution path
QuEra
neutral atom · quantum-cloud execution path
D-Wave
annealing · quantum-cloud execution path
Tracked public artifact
CycloneDX 1.7 · qstrike-c2
- Format
- CycloneDX
- First public asset
- AES-256
- SHA-256
- 8912c569429980f9a5e73e0755e267b8a52c46aa10bac56c259484b2b01e7798
- Snapshot in this page
- release 11f036d3 · generated 2026-07-30
Synthetic public target — not client evidence and not proof of live quantum-hardware execution.
The SHA-256 above is computed at build time from the snapshot bytes bundled with this page. The live publisher serves the current QStrike release; its checksum file is the authority for the bytes it returns.
Live publisher
Claims this boundary excludes
- No direct break of RSA-2048, ECC-256, or client keys.
- No live provider jobs or connected quantum hardware in the public runtime.
- No claim that a future-machine resource estimate is a demonstrated break.
- No provider endorsement implied by a quantum-cloud execution path.