← The Hub qmarket :8824 · verified 2026-09-12 · v2 scenario pass
for sellers — rigs to racks

Sell your compute

People selling compute to people, paid in QALS-backed credit. Pick your track: a home rig earning while idle, or data-centre capacity sold by the GPU-hour. The trust mechanics — escrow, attestation, slashing, reputation — do the policing, so nobody has to trust anybody.

0% platform fee You keep your market price — every cent a buyer pays for your compute settles to you. Founder policy, 2026-09-12: no marketplace fees; the token spread is the network's margin. (Chain usage is fee-sponsored too. Only the optional cash-out gate takes 0.5%, and only if you ever turn credit back.)

Bulk capacity, sold with receipts

Register capacity the way a data centre thinks: named nodes, a job kind, a price per unit, and a stake behind every promise. The market is live and proven — the full provider lifecycle passed test_market_v2.sh (30 assertions) on 2026-09-12, including slashing and delisting.

What pro listing looks like

  • Priced per job kind — render or inference today, priced in cents per unit off the bench ladder.
  • Pricing tiers — the bench oracle publishes a price floor per kind; your market price sits above it as the quality premium. Multiple providers at different prices = the live price ladder buyers see on qalx.
  • Staking for trust (and standing) — the stake is your bond. Bigger stakes signal seriousness; every job settles against it.
  • Remote & dedicated capacity — the provider agent (:8850) polls for jobs and executes locally or on remote automation — the RunPod-style pattern maps onto the same provider loop, artifacts via object storage, output hash anchored at settle.
  • Buyer vetting, your choice — set require_qalid: true and the market refuses any job without a valid QAL ID proof (single-use nonce, replay-proof), checked before escrow.

Why enterprise buyers trust it

  • On-chain receipts — every settle writes an anchored receipt; nothing is a promise on someone's database.
  • Challenge & verify — a dispute triggers recompute against the anchored output hash. Anchored evidence is the honest seller's defence.
  • Slashing with symmetry — a failed verification cuts the stake 50/50 (FloorVault/buyer), reputation −25, delist below 40. Honest work climbs reputation back.
  • Escrow, not invoices — the buyer's payment is a ledger hold placed before the job; settle is metered × your price. No 30-day terms, no chasing.

Reference price ladder bench oracle floors — market prices sit above

ClassReference priceJob kind
A100-class272 c/hourinference
RTX 4090110 c/hourgpu-render
L4-class69 c/hourinference

From qmarket/bench.py — measure, don't guess. Earnings accrue AU$1:1 in credit, visible per provider on GET :8824/earnings/<id>.

Onboarding checklist

  1. Register — with your stakeName, job kind, price, and the bond. One call: provider.py register --name dc-node-01 --kind inference --price 272 --stake 5000. The stake is a loopd agent you own — the market can slash it, nothing else.
  2. Stake goes on the booksYou appear in GET :8824/providers — price, reputation 100, stake listed. Buyers can see you're good for it.
  3. Benchmark — measure, don't guesspython3 qmarket/bench.py measures the work (sha256 throughput + tokens/s), writes price floors, and keeps your listing honest.
  4. List & runStart the provider agent: python3 qmarket/provider.py run (:8850). It polls, executes, returns output. Optionally set require_qalid.
  5. First job → first receiptEscrow hold → run → attested output hash anchored on Qalnet → settle at metered × your price. 0% taken. Earnings land as spendable credit.
⚠ Invite phase: capacity onboarding is accredited partners first, open listing later. If you're running GPUs seriously, talk to us now and get in before the queue.

Your rig, earning while you sleep

A gaming PC, a mini PC, any box with compute to spare. Register it, put up a small stake, and the provider agent takes jobs while the machine is idle. No one has to trust you — and you don't have to trust them. The money does the trusting.

The plain-English path today: repo + CLI · roadmap: one-click agent in the wallet

  1. Measure your machinepython3 qmarket/bench.py — measures the work, not the spec sheet, and suggests a price floor. Your earnings = market price × your machine's honest benchmark.
  2. Register with a stakeThe stake is skin in the game — a bond you can lose for cheating. It's why buyers trust a stranger's GPU. The market can slash the stake, nothing else you own.
  3. Start the workerprovider.py run polls the market and runs jobs you registered for. Today that's one command from the repo; the roadmap is a one-click provider agent inside the Qal Wallet compute tab.
  4. Watch earnings landCredit accrues AU$1:1 — spendable in chat, redeemable for services, no cap. Check GET :8824/earnings/<provider-id> or the wallet.
# 1. measure, don't guess (reference ladder: A100 272c/h · 4090 110c/h · L4 69c/h) python3 qmarket/bench.py # 2. register — name, kind, price (c/unit), stake python3 qmarket/provider.py register --name my-rig --kind gpu-render \ --price 110 --stake 2000 --description "4090 box, night hours" # 3. take jobs (serves the adapter on :8850) python3 qmarket/provider.py run # 4. earnings, AU$1:1 in credit curl -s http://127.0.0.1:8824/earnings/<provider-id>

What a job looks like

escrowbuyer's payment parked in a ledger hold
runyour machine executes the job
attestoutput hash anchored on-chain
paidsettles at metered × your price — 0% taken
⚠ Electricity honesty line: if your power costs more than your price earns, don't bother — the math box below shows the crossover. And the honest status of the money itself: the ledger runs on test cents today; no real dollars have moved (the sellable supply sits pre-endowed in the issuer wallet). You're earning track-record and reputation now.

Trust with teeth

Four mechanics do the policing — hover each for the plain words. Proven live in test_market_v2.sh: the cheating provider gets slashed twice and delisted; the honest one recovers.

Escrow-until-delivered The buyer's payment sits in a ledger hold while your machine works, then settles at metered × your price. You never chase an invoice; they never pre-pay a stranger.
Attested outputs Your output's hash is stamped into the shared record. Anyone can recompute the fingerprint and check it against the stamp — the job provably ran, in that state, at that time.
Challenge & slash A dispute triggers verification — recompute vs the anchor. If the anchor disagrees with you, the stake is cut 50/50 (FloorVault/buyer) and reputation drops 25. Two failed verifications = delisted.
Reputation You start at 100. Clean jobs hold or climb it; drop below 40 and you're delisted. Honest jobs climb reputation back — recovery is in the proof suite, not the brochure.

The money math estimate — formula shown, you decide

No fake numbers. The market price is set by providers (you), the platform takes 0%, and the formula is right there. Pick a hardware class, set your power price and how many hours you'd actually sell, and the box computes it with you. Demand is not guaranteed — that's why it's a range.

net = (price × hours × 30.4 days) − (watts × hours × 30.4 × $/kWh)
quiet · 4 h/day
busy · 16 h/day

Presets from the bench ladder (A100 272 · 4090 110 · L4 69 c/h) and bench.py assumptions (250 W, $0.30/kWh). Everything above is editable — this is your price and your power bill, not a promise. Earnings accrue as AU$1:1 credit; zero platform fee taken.

sell-compute funnel · classic theme · every number traceable to the corpus (qmarket/README · content/ground_truth.md · content/guides/selling-compute.md)
hub · qalx boards · guide · landing · ask the assistant