Node
Any device serving a share of a model — GPU, CPU, NPU or phone — earning KVR for the work it does.
A node is any device that serves part of a model: a GPU box, a CPU machine, an NPU device, or a phone. A node holds only its share — a layer window on the ring, or an expert slice in the swarm — and earns KVR weighted by exactly the work it performed. The live fleet has mixed AMD MI250s, NVIDIA GB10s and RTX Pro 6000s, a MacBook, x86 Windows CPU machines and mobile nodes in one network.
From download to payout
A node's lifecycle
join → slot bind / unit import / agent /control/join report → capabilities: backend · VRAM/RAM/CPU budgets · monitoring plan → planner assigns a layer window (or expert range) download → partial shard: only the tensors that window needs serve → run its share; pass boundaries / answer dispatch earn → units × layer_share × perf_tier → owner wallet
- Compute nodes earn per contribution unit, weighted by layer share and scaled by performance tier — no stake required.
- Nodes register under their owner's wallet; rewards settle to that wallet, non-custodially. Four distinct owner wallets each earning their layer share has been verified end-to-end.
- Capability data (backend, accumulation precision, resource budgets) decides what the planner may place on a node — and, in the swarm, which ranks it may serve.
- A node that can't provide resource monitoring is excluded from adaptive loading rather than trusted blindly.