How Spindle Connects GPU Work, Signed Receipts and Provider Claims

Start with the node and compute lane

Spindle’s proposed flow begins with the Docker node agent. It benchmarks the GPU, detects confidential-compute support, creates a node key and registers the node through a wallet signature on Robinhood Chain. Hardware capability decides whether the node can join the sealed lane or the open lane.

Follow the AI request

AI builders use the OpenAI-compatible gateway design for chat, embeddings and images. A request selects a compute lane. The scheduler chooses a suitable node using lane, VRAM fit, latency, stake and reputation. Sealed requests use the eligible confidential stack; open requests must be non-sensitive.

Link completed work to a receipt

The node emits a signed COSE receipt when a job completes. Verification checks its signature and metering against the gateway record. Verified work accrues in USDG and enters a cumulative Merkle tree, with an hourly root posted on Robinhood Chain.

Choose the claim route

A provider can inspect the intended claim flow for USDG, a canonical Stock Token or a virtual card. Quotes, liquidity, supported regions and program terms shape the available options. This site explains the v1.1 design and does not promise live availability, demand or earnings.