How Inference Works on TrueOpen
Model maintainers register models, and GPU providers register nodes. Once a user submits a task, the protocol selects a node to run inference. The result is returned to the user, followed by verification and settlement.
Model Maintainers Register Models
Model maintainers register the model, its runtime configuration, and its verification rules, and publish the applicable fees.
Register model → Define rules and feesGPU Providers Register Nodes
GPU providers register their nodes, stake funds, and declare which models they support and what computing resources are available.
Register node → Stake funds → Declare supported modelsUsers Submit Tasks
Users choose a model and runtime settings, optionally enable encryption for their inputs and outputs, and sign a task order. The protocol holds the task budget in escrow.
Choose model → Sign task order → Fund escrowThe Protocol Selects a Worker
The protocol uses a verifiable random function (VRF) to preselect candidates. After nodes submit their participation requests, the candidate list and selection weights are frozen. Randomness from a specified future block then selects the Worker.
Submit participation requests → Freeze candidates and weights → Select WorkerThe Worker Runs Inference
The selected Worker runs the specified model, generates the output, and records evidence of the computation.
Run model → Generate output → Record evidenceThe Worker Returns the Result
The Worker delivers the inference result to the user without waiting for verification or settlement.
Deliver result → User receives outputVerifiers Independently Check the Computation
Verifiers independently check the computation under the model’s verification rules, using either Logprob recomputation or sampled layerwise cryptographic verification. In the latter approach, Verifiers check proofs for fixed-point quantized models or perform numerical audits for floating-point models.
Check computation → Submit verification recordsThe Protocol Settles Fees On-Chain
Based on verification and dispute outcomes, the protocol distributes fees, processes refunds, and holds responsible nodes accountable. Earnings are released once the protocol’s release conditions are met.
Confirm outcome → Settle fees → Release earnings
Funds & Coordination
Commitments Enforced by Code
Users fund escrow before a task begins, and nodes reserve collateral from their stakes. After service is delivered, the protocol distributes fees according to verification results. Confirmed cheating triggers refunds and penalties for responsible nodes. Until verification and disputes are resolved, the associated earnings and collateral cannot be withdrawn in full.
