QMeshDocs

Introduction

QMesh runs quantum circuits as services on a peer-to-peer network, and records evidence of every run.

QMesh is an open-source research platform that treats quantum operations as network services. You submit an OpenQASM circuit to a coordinator. The coordinator discovers worker peers over libp2p, splits the circuit into fragments, reserves capacity on the peers, runs the fragments, and returns the result together with a provenance record you can verify.

Simulated qubits

QMesh runs circuits on Qiskit statevector simulation. It does not control quantum hardware. The network, the job lifecycle, the payment flow and the provenance records are real software, and every blockchain it uses is a testnet. See Scope for the full picture.

What you can do with it

  • Run a circuit across peers. Submit OpenQASM over HTTP and watch the job move from QUEUED to COMPLETED. See Basic usage.
  • Optimize a portfolio. Upload asset data and compare a QAOA run with classical baselines.
  • Price options and measure risk. Run option-pricing and risk jobs (VaR, CVaR, credit risk) through the same job model.
  • Pay per request. Expose a paid endpoint with the x402 402 Payment Required flow, settled in USDC on Algorand TestNet.
  • Verify a result. Every completed circuit job gets a provenance bundle with a Merkle root. See Provenance.

How a request flows

A request passes through five layers. Each one has its own page under Concepts.

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

Your app

Submit an OpenQASM circuit to the REST API, or paste it into the operator console.

Coordinator

Normalize the circuit, build an execution plan and split it into fragments. See Circuit planning.

Payments and registry

Charge for the request, either from prepaid credits or through an x402 payment, and look up the services that are available.

Peer mesh

Reserve capacity on each peer, then stream the fragments to them over libp2p. See Peers and discovery and Reservations.

Provenance

Hash the inputs, the plan and the fragment results into a bundle with a Merkle root.

Where to go next

Installation

Run the backend and the console on your machine.

Basic usage

Submit a circuit, poll the job and read the result.

Architecture

The pieces of the system and how they fit.

AI resources

Every page is available as Markdown: add .md to its URL, or use Copy Markdown at the top of the page. The whole site is indexed at /llms.txt and /llms-full.txt.

Scope

What is real, what is simulated and what is still experimental.

On this page

What you can do with itHow a request flowsYour appCoordinatorPayments and registryPeer meshProvenanceWhere to go nextAI resources