DeComp is a market for Apple-silicon GPUs. AI agents rent them by the five-second tick and pay over x402, settled on Hedera. Every job leaves a receipt anyone can check.
4 ticks · 20.0s ·0.0000 ℏ0.0625 ℏ0.1250 ℏ0.1875 ℏ0.2500 ℏ
Each block is one payment. The provider meters wall-clock GPU time on the device and sells it five seconds at a time at 0.0125 ℏ/s — so the most either side can be out of pocket is a single tick. Stop paying and the job is killed mid-flight.
DeComp only works because both halves exist: machines with idle GPUs, and agents that need one for eighteen seconds. Pick the half you're here for.
Add DeComp to Claude as a custom connector and ask for a render. It pays from your own wallet, per tick, and hands the result straight back into the conversation.
Set it up in three steps →I have a MacRun Decomp Node, set a price, and the registry advertises you. Payouts land in your own Hedera account tick by tick, with a dashboard that reconciles against the chain.
See the node app →Nothing here is a private arrangement. A job is an ordinary HTTP exchange where the interesting status code is 402 — and it repeats every five seconds until the work is done.
DeComp ships as a remote MCP server with its own OAuth, so any MCP client can use it — Claude, or anything else that speaks the protocol. No terminal, no .env, no key on your side.
In Claude, open Settings → Connectors → Add custom connector and paste the server URL. Claude registers itself — there is no JSON to edit and no API key.
https://mcp.decomp.cloud/mcpHosted endpoint coming soon — until then, run bun run connector and point Claude at your own tunnel.
Claude opens the DeComp login page. Sign in with an email and a Hedera wallet is provisioned for you on the spot — you never see a private key, and neither does the connector.
That's it. Jobs run on a real Apple-silicon GPU, paid from your own wallet, capped by a budget you set per call.
render a mandelbrot at 2048×2048, 3000 iterations
{
"jobType": "mandelbrot",
"params": { "width": 2048, "height": 2048, "max_iter": 3000 },
"maxBudgetHbar": 2
}Done — rendered on PROVIDER_1 in 20.0s.
Decomp Node is a desktop app. Sign in with an email, and it provisions a Hedera account keyed by your own wallet — then shows you exactly what the chain says you earned.
Settlements land in your own account as the job runs — not at the end, not on a payout schedule.
The account, the topics and the token are set up on first sign-in. You choose a node name and a price.
Every figure on the dashboard is rebuilt from the audit topic and the mirror node, with a link to each transaction.
macOS on Apple silicon · M1 or newer · free to run
This is a real message off the audit topic — the whole trust model fits in it. Four fields are doing the work.
{ "schema": "decomp/job-audit@1", "jobId": "job_9f2c41a7", "jobType": "mandelbrot", "provider": { "id": "PROVIDER_1", "account": "0.0.10490091" }, "agent": "0.0.10490089", "asset": "0.0.0", "tickSeconds": 5, "transactions": [ "0.0.7162784@1789178972.245387934", "0.0.7162784@1789178978.208479584", "0.0.7162784@1789178983.334990514", "0.0.7162784@1789178988.117402265" ], "totalPaid": "25000000", "wallClockS": 20, "status": "completed"}A registration only counts when the account that paid for the HCS message is the account it names. Nobody can list someone else's payout address.
Readers check that the agent named here also published the record. A provider can't fabricate earnings from an agent that never bought anything.
Each id is a real Hedera transaction. Replay them against the mirror node and the amounts either add up or they don't — no trust in this record required.
25,000,000 tinybars against 20 metered seconds is 0.0125 ℏ/s — the price the provider advertised before the job started.
Measured GPU time, in five-second ticks. The provider meters wall-clock time on the device and each new tick is a fresh payment challenge — if payment stops, the job is killed rather than run for free. You are never billed for time the GPU didn't spend on your job.
Nobody hands one over. Every account — yours, the providers', the operator's — is a Privy wallet used as a signer. Signing happens inside Privy's enclave; DeComp only ever sees signatures, and there is no Hedera private key in the repo, the desktop app, or the connector.
You need a wallet, and one is created for you on first sign-in with an email. Jobs settle in HBAR, or in DCC — an HTS compute-credit token — if a provider accepts it.
A fixed, validated menu: a dense matmul benchmark on MLX or PyTorch MPS, and a Mandelbrot render that comes back as a PNG. The runner refuses to execute on CPU, so a job either uses the GPU it was paid for or fails.
Every finished job publishes an audit record to a Hedera Consensus Service topic, listing each settlement transaction. Anyone can replay a provider's entire earnings history from the topic and the mirror node without trusting DeComp at all.
Yes. A node can connect out to a relay instead of taking inbound traffic, so it needs no public IP, domain, or tunnel of its own. The relay holds no keys — it verifies a connect-time signature against the mirror node.
Rent a GPU from your AI tool in three steps, or put an idle Mac to work. The network is live on Hedera.