From machine to settlement
Follow one machine capability as it becomes a proof, a reservable VSlot, an execution, and finally a settlement. Each step is a first-class object in the protocol.
protocol · walkthrough · representative objects
Follow one full journey
Try the consumer, provider and developer paths end to end. Every state is a DEMO state — nothing is broadcast.
Consumer journey
Describe what you need
Tell VSlot what to run on. The request maps to verifiable capability primitives.
A physical host. It is identified by a machineId and can be verified on-chain as active.
object · Machine
View exampleThe machine declares CPU, RAM, GPU, VRAM, CUDA, network and region as canonical JSON.
object · Capability
The agent signs the capability and binds it to the machine — the claim becomes evidence.
object · Proof
Verified capacity is sliced into a priced, time-bound window with committed resources.
object · VSlot
View exampleA consumer locks the window and bonds on-chain; the commitment is fixed.
object · Reservation
The consumer submits a workload addressed to the reservation with a resource ask.
object · Job
The provider's agent runs the job inside a sandboxed container on the reserved capacity.
object · Execution
The executor signs usage — what ran, for how long, on which GPU — as a verifiable report.
object · UsageProof
Usage resolves to payment, bond release or slash — settled against verified proof.
object · Settlement