Compute Marketplace
Compute jobs are dispatched deterministically to active providers, settle through escrow, and preserve a replayable receipt/proof/challenge trail.
Launch scope
T1 signed/optimistic, T2 redundant/quorum, and T3 hardware-attested verification have different prerequisites. Build features, active policy, provider state, verifier material, and trust anchors determine the modes a network can accept.
Explorer and clients call sigil_listProviders, sigil_listComputeJobs, and the compute audit methods rather than substituting sample provider data.
Verification boundaries
Compute execution remains off chain. Receipts, commitments, challenges, and accepted settlement records belong to the chain. Lumen has a narrower sampled-commitment verification scope; TEE verification needs a complete trust-material and policy path.
Validators
Validator operation requires the selected network configuration, identity and stake policy, custody, synchronization, and activation checks. Read the current set instead of assuming a fixed validator count.
DEX
The Sigil DEX is a deterministic constant-product AMM with typed pool, liquidity, swap, quote, position, and event surfaces.