QAISS is building a neutral quantum-AI coordination layer. Follow the public roadmap and verify every claim.

Reproduction bounties

Bring the hardware. We bring the proof.

Each bounty asks someone with the right hardware to re-run a passport. Submissions are checked automatically: simulators bit-for-bit, quantum hardware statistically. Every status on this page is computed by re-running the submission, not taken on trust.

3 open bountiesRewards: credentials · token/USDC after counsel

Open bounties

What we need verified

These are the project’s real gaps. QAISS has no NVIDIA GPU and no QPU access, so its GPU and QPU backends cannot be marked verified until someone runs them.

B-001Open · no submission yetCheck: bit-for-bit

Reproduce GHZ on NVIDIA cuStateVec

Run the GHZ passport on an NVIDIA GPU with the connector's cuStateVec backend. A matching hash moves gpu.custatevec.fp64 from untested to verified.

Target passport
ghz.json
Accepted backends
gpu.custatevec.fp64
Reward
GPU Operator · cuStateVec credential
python -m qaiss_cuquantum run ghz.json --backend gpu -o submission.json
B-002Open · no submission yetCheck: bit-for-bit

Reproduce rotations on NVIDIA cuTensorNet

Run the rotations passport with the connector's cuTensorNet backend on an NVIDIA GPU. A matching hash verifies gpu.cutensornet.fp64.

Target passport
rotations.json
Accepted backends
gpu.cutensornet.fp64
Reward
GPU Operator · cuTensorNet credential
python -m qaiss_cuquantum run rotations.json --backend gpu-tn -o submission.json
B-003Open · no submission yetCheck: statistical (TVD ≤ 0.15, ≥ 1000 shots)

Run a Bell pair on an Origin Quantum QPU

Submit the Bell circuit to a real Origin Quantum processor through the connector's cloud adapter. This is the first QPU result in the registry, compared statistically with the ideal distribution.

Target passport
bell.json
Accepted backends
qcloud.origin.*
Reward
QPU Operator · Origin credential
QPANDA_QCLOUD_API_KEY=… python -m qaiss_cuquantum run bell.json --backend origin-cloud --origin-backend <QPU> -o submission.json

Submit

How to submit

  1. Set up the connector (GPU path, or Origin cloud) and run the bounty’s command.
  2. Check the result below. It runs the same verification the site and CI run.
  3. Open a pull request that adds it as bounties/submissions/<bounty id>/<your name>.json. CI re-verifies it with the Python connector, and the page lists it once merged.

The public repository opens when the project publishes its GitHub. Until then, keep your verified file; it remains valid. Hardware runs also need the provider’s job id for review.

    Release notes

    Engineering updates,
    not hype.

    Research drafts, releases, and every change to a public claim. No price talk.

    Subscriptions open once the project publishes its privacy policy and mailing endpoint.