Bonded identity and receipt checks support node accountability.

Give each node a bonded identity

The Spindle design links a node key to an ERC-8004 identity owned by an operator wallet. Registration records GPU class and confidential-compute capability. The identity gives the scheduler and receipt verifier a consistent reference for the node that served a job.

Connect stake to the node role

SPDL is an access and routing token in the specification, not the unit of provider earnings. The minimum stake scales with GPU class. The design uses stake and reputation alongside VRAM fit, latency and compute lane when choosing a suitable node for a job.

Check the work as it arrives

The receipt verifier checks the node signature, matches the job to billing and compares measured units with the gateway record. Known-answer canary jobs and periodic hardware probes are additional checks in the design. These are verification mechanisms, not a guarantee of output correctness.

Make the limits visible

Completed buyer-funded work determines earnings. A node’s hardware does not create a guaranteed payment, and consumer GPUs are not confidential compute. These limits matter when comparing the open lane with the sealed lane (in testing) or deciding whether to supply a GPU.