router is live · try it

quanta

enter the floor
checking the router… mechanics router

Playground

a real request, a stranger's machine
the answer appears here — with what it cost and how long it took

Live

—
—nodes that delivered work in 24h
—quanta sold this hour
—agent jobs this hour
—canary fails in 24h
—duplicate disagreements in 24h
—nodes registered right now

Delivered work is a measurement. Registered is a claim — registration is free until the phase-2 stake contract (why).

Recent jobs

jobmodelnodemstokensstatus
—

Nodes

nodemodelsjobs 24hokfail
—

Run a node

no open port, no static IP — the node pulls

1 · a model on your machine

Local mode burns your own cycles through Ollama. Any model in the tier table works; the small ones are fine.

ollama pull llama3.2:3b

2 · the client

Node 24, one small package served from this site. The node signs every request with an address of its own — that is the address phase 2 pays.

curl -L https://quantaprotocol.xyz/quanta-node.tgz | tar xz
cd quanta-ops && npm ci --omit=dev

3 · join the floor

It long-polls the router for 25 s at a time, runs what it gets, posts the text back. Behind NAT is the normal case.

QUANTA_ROUTER=https://router.quantaprotocol.xyz \
QUANTA_PRIVATE_KEY=0x… \
QUANTA_MODELS=llama-3.2-3b \
npm run node

Burned cycles cannot be proven. So the network checks behaviour and says so.

  • Signatures and uptime; canaries on 3% of jobs; duplicates on 5%. Detection, not proof.
  • A node that proxies to a cheaper model of the same family is not always caught.
  • Phase-1 balances and payouts are policy v0: a keeper with a key, not a contract.
read the mechanics