QMesh
One request travelling through the five layers of QMeshA request, shown as a glowing cube labelled your circuit, falls through five layers. Your app: laptops and a tablet send a quantum circuit. Coordinator: servers named plan, reserve and run split it up and plan the work. Payments and registry: payment terminals and ledger drums take payment per run and find workers. Peer mesh: everyday laptops, towers, phones and boards run the pieces. Provenance: receipt printers produce a receipt that proves what ran, and the receipt travels back up to your app.ONE REQUEST, FIVE LAYERSL5RECEIPTRECEIPTRECEIPTL4L3402USDC402USDC402USDCL2PLANRESERVERUNL101 YOUR APPYou send a quantum circuit02 COORDINATORSplits it up and plans the work03 PAYMENTS AND REGISTRYYou pay per run; workers are found04 PEER MESHEveryday devices run the pieces05 PROVENANCEA receipt proves what ranYOUR CIRCUITRECEIPT

Simulated qubits · real network · testnets only

Quantum, run as a network

Get started Open the console

README

A research platform that runs quantum circuits as network services. A coordinator plans a circuit into fragments, reserves worker peers over libp2p, runs the fragments on Qiskit simulation, and records a verifiable provenance bundle for the result.

curl -X POST "$QMESH/api/v1/circuits/submit" \
  -H "Content-Type: application/json" \
  -d '{"circuit": "OPENQASM 2.0; …"}'

Submit an OpenQASM circuit. The API returns a job id right away; poll the job for the result.

Built on

py-libp2pQiskitFastAPINext.jsMongoDBIPFSKuboAlgorand x402Ethereum SepoliaChainlinkRobinhood Chainpy-libp2pQiskitFastAPINext.jsMongoDBIPFSKuboAlgorand x402Ethereum SepoliaChainlinkRobinhood Chain

Features

01

Distributed circuits.

Submit OpenQASM, get a plan of fragments, and watch peers run them.

OpenQASMlibp2pQiskit
02

Job lifecycle.

Follow every job from QUEUED to COMPLETED over a plain REST API.

RESTprogressresults
03

Peer discovery.

Workers announce themselves over GossipSub; the coordinator tracks their health.

GossipSubheartbeatstrust tiers
04

Reservations.

Reserve a peer before sending work, with automatic fallback when one fails.

preparecommitfallback
05

Machine payments.

Charge per request with the x402 flow, settled in USDC on Algorand TestNet.

402USDCAlgorand
06

Provenance.

Every completed run gets a hashed bundle you can verify, publish and anchor.

SHA-256MerkleIPFS

© 2026 QMesh · Open source under Apache 2.0 · distributed-quantum.com