sigil

Double-click anywhere. I know everything about Sigil.

or I can help you find anything

Ask about Sigil — or anything in the ecosystem

Enter to askEsc to close

An on-chain market for AI compute.

Buy inference, training, or any agent workload from a marketplace of providers. Pay through MINT escrow. Settle on signed receipts. Audit every job with on-chain proof. Operators bring the hardware — Sigil brings the trust.

sigil · liverunning
BUYERSmarketplacePROVIDERSBUYERbuyer:atlas-corpBUYERbuyer:ventus-aiBUYERbuyer:l1fe-opsBUYERbuyer:nyx-labsT1·T2·T3provider:gpu-eu-3T1·T2provider:aki-meshT3provider:tee-cluster-7T1provider:edge-vegaSETTLED · 1,8420 in flightT1 receipt · T2 quorum · activation-gated T3 · settlement gated by tier
01 / 07
Market

The compute market

An on-chain market for AI compute.

Buyers fund jobs. Providers deliver work. The chain holds the escrow, verifies the receipt, and settles MINT to the provider. The trust isn't in the operator's word — it's in the chain's record.

Step 1 · Fund

The buyer funds escrow on chain.

A MINT deposit lands on the buyer's rail. The escrow is locked against the job specification — the chain knows what the funds are for and which provider class is allowed to claim them.

Step 2 · Dispatch

The contract picks a provider.

An authorised dispatcher contract reads the job spec, picks a provider, and writes the binding. The job ticket carries a provider-bound stamp from this point forward.

Step 3 · Execute

The provider runs the workload.

The job drops from the buyer rail to the provider rail. The provider runs the inference, training, or arbitrary workload. The escrow remains locked on chain throughout.

Step 4 · Receipt

A signed receipt returns to chain.

The provider submits a receipt: the result commitment, the execution timing, and — for tier-3 workloads — a hardware attestation. The chain verifies the receipt against the job spec.

Step 5 · Settle

MINT moves. Once. Provably.

The escrow drains from the buyer side and lands on the provider side. The transfer is atomic with the receipt verification — no half-settlements, no operator overrides.

Step 6 · Audit

Every step is on chain, forever.

Job spec, provider binding, receipt, settlement — all four records persist on chain. Buyers can replay any historical job to verify it ran as claimed. Providers can prove delivery without trusting the buyer's memory.

Three tiers of trust

Pick the proof. Pay the price.

Three settlement tiers, one common interface. Tier 1 settles on a signed receipt from the provider. Tier 2 settles only when a quorum of providers agrees on the result. Tier 3 binds the workload to a hardware-attested enclave. Buyers pick the assurance that matches the job.

VERIFICATION TIERS · settlement guarantees ascendingidle · T1 · TIERReceiptsigned-result acceptanceprovider DID + Ed25519 signature on result_commitmentT2 · TIERQuorumk-of-n provider agreement⅔+ stake-weighted agreement aggregated within MACA epochT3 · TIERTEE Attestedhardware-rooted executionvendor attestation chain · allowlist · freshness · receipt-boundbuyer picks the tier at posting time · settlement gated by tier verification

The full lifecycle

Fund. Dispatch. Execute. Settle.

Every job moves through the same rail. The buyer funds MINT escrow. The chain dispatches the job to a provider. The provider executes and submits a signed receipt. The chain verifies, settles, and writes the audit trail. Same path, every time.

JOB LIFECYCLE0 jobs in flightBUYER · 01Postescrow ↗PROVIDERS · 02BidopenBUYER · 03AwardfrozenPROVIDER · 04ExecuteworkloadPROVIDER · 05SubmitcommitCHAIN · 06Verifyverify$PROVIDER · 07Settlerelease ↘buyer posts, providers bid, chain settles · MINT escrowed end-to-end

Compute that proves itself.

Buyers fund jobs. Providers deliver receipts. The chain settles. Every step verified, every payout traceable.