Providers with a record
Providers register capabilities and economic commitments. Selection can consider price, latency, capacity, liveness, verification tier, and authority requirements.
Compute, with a settlement layer
Put compute to work. Account for the result.
Connect providers, funded work, signed receipts, and challenges through Sigil’s native compute marketplace.
Compute MarketplaceIllustrated study
Input / work / result
Work happens off-chain. Its agreement leaves a record.
01 / Built for a purpose
The work happens off-chain. The agreement is recorded.
A compute job needs more than a machine. It needs a provider, an agreed payment, a result, and a way to challenge that result. Sigil gives those relationships a shared settlement surface while the workload runs on the appropriate hardware.
Fund work before it runs
Escrow separates the consumer’s available balance from money committed to compute. Settlement pays against a receipt under the applicable policy.
Verification that matches the workload
Provider signatures establish attribution. Quorum approaches add independent agreement. Supported TEE configurations add hardware-attestation checks. Each tier has a different trust model.
A challenge path
Receipt challenges and configured resolution rules make disputed work part of the protocol. Payment and challenge outcomes become records applications can inspect.
Artifacts that continue the workflow
A result can become an evidence anchor, a storage commitment, or input to a later contract. Compute fits into an agent’s wider work rather than ending at an API response.
02 / From intent to outcomeA clear path through
A clear path through
compute marketplace.
- 01
Choose the provider and policy
Match the workload to provider capabilities and the verification standard the application needs.
- 02
Fund and execute
Reserve payment, dispatch the off-chain job, and collect the required result and receipt material.
- 03
Verify and settle
Submit the receipt, apply the active checks, and resolve any challenge through the network’s supported path.
The details matterGood questions.
Good questions.
Clear answers.
Does Sigil run GPU inference in a block?
No. Compute runs off-chain. The chain processes provider, escrow, receipt, and challenge state.
Does every receipt prove that a model ran correctly?
No. The guarantee depends on the verification tier. A signature, quorum, TEE attestation, and sampled Lumen commitment support different claims and should be selected accordingly.
Keep exploringOne capability.