About · pre-launch
Compute should have a market.
Openmesh is a decentralized cloud network and the exchange being built on top of it — the first futures market for compute, on Solana. Real infrastructure capacity — GPUs, vCPU, RAM, storage and bandwidth — is verified, tokenized, priced on an order book, and delivered to real workloads.
Instruments11 at launch across cloud compute and physical hardware
DeliveryQuarterly contracts · cash or physical settlement
CollateralUSDC, cross-margin, on-chain vault
ChainSolana · ~400 ms blocks · sub-cent fees
Why compute needs a market
Today the physical compute market and the financial market operate separately. Data centres, GPU operators and infrastructure providers own future capacity but have limited ways to finance, price or sell it in advance. Traders want exposure to the growth of compute and have no transparent market behind it. AI companies need future capacity and depend on private contracts and fragmented providers.
Openmesh connects these markets. Compute supply is financed, priced, traded and delivered on one exchange: the Openmesh Exchange for compute and GPU futures, the Infrastructure Capacity Market for verified future supply, and the Compute Settlement Layer that turns traded capacity into real usage.
Principles
- Verified supply only. No synthetic compute. Every physically-settled contract is backed by attested infrastructure and an operator bond.
- One collateral. USDC for margin and settlement keeps risk simple and transparent.
- Open price. A public forward curve for every instrument and quarter, the way oil, power and metals are priced.
- Delivery is real. A contract for Q1 compute resolves into Q1 compute on the Openmesh network.
Instruments
Each instrument is a standardized unit of compute with a reference index. Instruments are grouped into two categories.
REF instruments are long-run reference indexes (USD per physical core, per FP32 TFLOPS at launch MSRP, per TB, per Gbps). They publish continuously and are not tradable at launch.
Contract specification
- Delivery quarters. Q4 2026, Q1 2027, Q2 2027, Q3 2027 at launch; a new quarter lists as the front one expires.
- Contract size. 1 unit of the instrument (1 GPU-hour, 1 vCPU-month, 1 GB-month, 1 TB-month, 1 TB egress). Minimum order 100 units.
- Tick size. 0.001 for prices under 2; 0.01 under 20; 0.05 above.
- Quote currency. USDC.
- Expiry. First day of the delivery quarter, 00:00 UTC. Trading halts 1 hour before expiry.
- Settlement. Cash at the final index, or physical for holders who elect delivery before the last trading day.
- Perp-style contracts. GPU and vCPU also list a non-expiring contract with 8-hourly funding against the reference index.
Margin & risk
- Cross-margin. One USDC collateral account per wallet across every instrument and quarter.
- Initial / maintenance margin. 5% / 2.5% for GPU and vCPU; 10% / 5% for RAM, storage and bandwidth. Leverage up to 20× on GPU.
- Liquidation. Keeper-driven partial liquidation at maintenance margin, with a 1% penalty split between the liquidator and the insurance fund.
- Insurance fund. Seeded by the protocol, grown from fees and liquidation penalties; backstopped by the LP vault and, last, by the native token.
- Fees. 0.02% maker / 0.05% taker, with tiered discounts for native-token stakers.
Reference index
Every instrument has a reference index published on-chain. It is computed from observed transaction prices on the Openmesh network, blended with public cloud list prices and spot hardware markets, outlier-filtered with a median-of-sources rule, and published every slot batch. The index fixes the final settlement price at expiry and drives perp funding.
Capacity tokens
A capacity token is an SPL (Token-2022) mint representing a claim on a defined amount of compute in a defined delivery quarter — for example 512 GPU-hours of GPU in Q1 2027. Tokens carry metadata for site, hardware specification, attestation hash and delivery window.
- Verification. Operators attest inventory, power and network through the Openmesh node agent. Only verified capacity can be minted.
- Bond. Operators stake the native token as a USD-value bond against non-delivery; the bond is slashed if delivery fails.
- Financing. Operators sell capacity tokens forward on the order book for USDC before the window opens.
- Redemption. Tokens are burned when the workload is delivered and metered.
Settlement
- Trading. Position held on the order book, cross-margined in USDC.
- Expiry. The delivery-quarter index is fixed. Cash-settled positions close.
- Settle. Physically-settled holders receive a redemption right on specific infrastructure.
- Deliver. Workloads run on the committed capacity through the Openmesh network; usage is metered and reconciled on-chain.
Architecture
Seven layers. Physical supply, verification and oracles, and capacity tokens form the physical stack. Settlement and the on-chain exchange programs form the financial stack. Off-chain services and applications provide access. Matching runs off-chain with on-chain custody, margin and settlement — the pattern that scales on Solana today.
See the layer and token diagrams →
Token
The native token is the security and governance asset. It is never used as margin or a settlement currency. It is used for operator and keeper bonds, governance over listings and risk parameters, fee-tier discounts, and as the final backstop behind the insurance fund. USDC trading fees flow to the treasury for buybacks and insurance.
API & SDK
A WebSocket market-data feed, a REST trading API and a TypeScript SDK ship with launch. Reference pricing for every instrument is available now in the app.
GET /v1/instruments
GET /v1/markets/{instrument}/{quarter}/book
GET /v1/index/{instrument}
WS wss://…/v1/stream?channels=book,trades,index
Launch
Openmesh Exchange is coming to Solana soon. Join the waitlist for the launch date, whitelist access and the opening market list. Infrastructure owners can apply to list capacity at launch. Partners and investors: hello@openmesh.network.