FAQ
Short answers to the questions people ask first.
No. Circuits run on Qiskit statevector simulation. QMesh is a proof of concept for orchestrating quantum operations as network services, not a hardware control stack.
The software is: a coordinator and workers exchange discovery messages, reservations and fragments over py-libp2p. In local development the workers run inside the backend process, so it is a controlled demo network. An example script can start an external node, but an open network of third-party nodes is not finished.
No. Payments use Algorand TestNet USDC, and every other chain QMesh touches is a test network.
That a recorded result has not changed since it was recorded. It does not prove hardware execution, scientific correctness or peer honesty. See Provenance.
OpenQASM 2 or 3 style text. Each operation is mapped to one of eleven service types, and any gate the parser
does not recognize becomes a programmable_gate. See Circuit planning.
Read the error field on the job. The usual causes are a circuit the parser rejects, no peer offering a
required service, or a block that failed on every assigned peer. See Jobs.
No. Every example in Basic usage calls the backend directly. The x402 payment gateway is the exception: it runs in the console's server routes.
Algorand (x402), Base Sepolia, Ethereum Sepolia, Starknet Sepolia and Robinhood Chain (read-only), plus Stripe, Chainlink, ENS, NEAR AI Cloud, Groq, OpenRouter, Coinbase CDP, IPFS and Filecoin through Lighthouse. Most are testnets. See the integrations overview.
Pages describe what is merged into main. Work in an open pull request is listed on the
roadmap and flagged where it would change a page.
Yes, under Apache 2.0. The code is at QMeshPy/distributed-quantum.