Roadmap
Work in review and ideas that exist only as issues. None of this is a promise.
This page lists what is not in main yet, as of 1 November 2026. It comes from the open pull requests and issues of
QMeshPy/distributed-quantum. The maintainers call the plan a proposal,
and the epic (#1) sets these ground rules for all of it:
- Testnet first. No mainnet code path is turned on without an explicit maintainer decision.
- No secrets in the repository, logs, prompts or browser bundles.
- Chain logic stays behind the chain registry.
- The platform runs on simulators. No feature is described as running on quantum hardware.
What already shipped is on the integrations overview.
In review
| Work | What it changes | Pull request |
|---|---|---|
| Pay-per-fragment payouts | Workers are paid per fragment in USDC, capped at the job's credit hold. A failed job is now charged for the fragments that finished. | #104 |
| Stripe Connect Express | Workers can opt in to cash out to a bank or stablecoin wallet. | #122 |
| Wallet portfolio analyzer | VaR and CVaR on an address's on-chain holdings, read-only. | #123 |
| EtherCalc workbooks | Persistent, shareable spreadsheets for experiment results, with IPFS versions. A draft, off by default. | #105 |
Proposed: payments and agents
| Idea | Issue |
|---|---|
| One x402 paywall across Base, Solana and Algorand, with dynamic pricing | #5 |
| Paid x402 endpoints for risk, finance and pharma services | #6 |
| A public MCP server that charges by x402, and an agent that pays x402 | #7 |
| Escrow-backed reservations | #9 |
| Tempo and Machine Payments Protocol sessions | #11 |
| Any-token funding and payout-token choice through Uniswap | #12 |
| Stripe crypto on-ramp for funding escrow | #78 |
| Off-ramp from the ledger balance, and documenting payout modes | #111, #112 |
| Quadratic funding rounds for research proposals (a first attempt, #99, was closed unmerged) | #17 |
| On-chain optimization bounties with verifier contracts | #20 |
| Random re-execution audits of worker fragments | #27 |
Proposed: more chains
| Idea | Issue |
|---|---|
| Base mainnet-readiness safeguards, Basenames and portable reputation | #14 |
| Escrow, wallets and x402 on Arbitrum | #15 |
| OP Stack support (Optimism, Unichain-ready) in the registry | #16 |
| Solana wallets, Solana Pay, memo anchors and a Toju SOL storage route | #24 |
| Chainlink CCIP cross-chain funding and payout, and CRE-driven escrow release | #26 |
| NEAR Intents deposits and TEE-held agent keys (research) | #30 |
| Zcash shielded fee payments | #13 |
| Hyperliquid read-only market data and backtests | #32 |
Proposed: the content layer
The epic #43 covers Helia in the browser, Kubo as the platform node and Boxo where needed. Open items include draining the pin retry queue (#44), a server-side pinning broker (#45 and #46), pinning as a CAR (#48), versioned record schemas (#50), export and import as a CAR (#52), several spikes (one Helia node per browser, large artefacts, IPNS feeds, Kubo pubsub bridged to GossipSub), a CID allowlist and takedown denylist (#72) and an IPFS adapter for provenance verification (#74).
Where to follow along
Watch the epic and the pull request list. Each integration page links the pull requests that built it.