Draft. This brief has not yet been reviewed or approved by the project owner or by counsel. Statements about the token reflect on-chain data only; nothing here is investment, legal or tax advice.
1 · Summary
QAISS is an independent project building a neutral coordination layer for quantum, AI and high-performance computing. Its core asset is an open, verifiable description of a quantum workload — the Workload Passport — together with adapters that run it on different backends and produce results anyone can re-check. The project measures value against classical baselines and does not claim quantum advantage.
2 · Problem
- Simulators and hardware expose different interfaces, so workloads are hard to move.
- Published results often lack the hardware, versions, precision or noise settings needed to reproduce them.
- Useful work is hybrid, and classical baselines are routinely omitted.
- Newcomers struggle to move from tutorials to reproducible experiments.
3 · Approach
- Passport first. A manifest records circuit, backend, precision, noise model, seed and shots, plus SHA-256 digests of the canonical circuit and output (specification).
- One sampling contract. Every compliant adapter uses the same seeded sampler, so identical inputs give bit-identical outputs (adapter specification).
- Verify anywhere. The browser verifier re-runs any supported passport and rejects altered results.
- Classical baseline required. Every research track names its baseline (10 tracks published).
- Status, not promises. Each of the 29 architecture components carries a public status.
4 · What exists today
| Capability | Evidence | Status |
|---|---|---|
| In-browser fp64 state-vector simulator | /lab · unit tests in scripts/qsim.test.ts | Live |
| Workload Passport v0.1 + verifier | /lab verifier · tamper test | Prototype |
| Python connector, CPU reference | Parity with browser on all fixtures · /gpu | Prototype |
| NVIDIA cuStateVec backend | Code complete; not executed on a GPU | Untested |
| Tensor-network backend (CPU) | Parity with browser on all fixtures; < 1e-12 vs state vector on random circuits · /gpu | Prototype |
| Origin Quantum pyqpanda3 CPUQVM backend | Parity with browser on all fixtures; < 1e-12 on random circuits · /lab | Prototype |
| Origin Quantum Cloud adapter | Written against pyqpanda3.qcloud; never run (no API key) | Needs access |
| NVIDIA cuTensorNet backend | Code complete; receives the verified network; not executed on a GPU | Untested |
| Benchmark protocol v0 | /benchmarks | Prototype |
| Quantum hardware access | None | Planned |
5 · Integration path
- CPU reference — done; defines the contract.
- NVIDIA GPU (cuQuantum) — run the connector’s GPU parity test on NVIDIA hardware; record device and driver. Requires licence review of NVIDIA components before any redistribution.
- Additional simulators — adapters for open-source frameworks, certified with the same fixtures.
- Authorized quantum cloud — only with documented provider access and permission; hardware results compared statistically, never by hash.
6 · Token decision record
| Network / standard | Solana · SPL Token |
| Mint address | qAiSsY4QBC75SGeFnrfujt4LTgZyCqinEyD11x5SR6f |
| Supply | Read live on /token (≈ 822.8 M at last review) |
| Mint / freeze authority | Both renounced on-chain — supply cannot increase; accounts cannot be frozen |
| Utility | None confirmed. Proposals only (see /token) |
| Allocation, vesting, treasury, liquidity policy | Not published |
| Why a token is necessary | Not yet justified by the project owner — required before any utility is promoted |
| What the token is not | Not equity, ownership, revenue share, a guaranteed access right or a profit instrument |
| Quantum exposure | Ed25519, like all Solana assets — not quantum-secure |
7 · Risks & limitations
- No quantum hardware is connected; all results are classical simulations.
- GPU parity is unproven until run on NVIDIA hardware.
- Token market data is thin and can be manipulated; low liquidity means sharp price moves.
- Legal entity, team and jurisdiction are not yet published.
- Third-party technologies (NVIDIA, Origin Quantum) carry their own licence terms; no partnership exists.
8 · Review & governance
Technical claims are tracked in the public claim ledger with source, owner and review date; status changes are recorded in the changelog. An external scientific review process — reviewers identified by role and expertise, conflicts disclosed — is planned before benchmark results are published.
9 · Open questions for the project owner
- Legal entity, jurisdiction and team to be disclosed.
- Licence for the website code and the connector.
- Token allocation, treasury controls and liquidity policy.
- Whether a token is necessary for the product, and which utility (if any) survives legal review.
- Official community channels, contact and security addresses.