Ritual.Demo

Infrastructure

RitualWallet & Job Lifecycle

Every precompile call is prepaid through RitualWallet, and every async call is tracked through the same 9-state lifecycle — the plumbing every feature on this site sits on top of.

◇Connect the demo wallet (top right) and deposit below — it's shared across every page on this site.

Async Job Lifecycle

Interactive simulationAsyncJobTracker· 9 states

Every async precompile call — HTTP, LLM, agents, multimodal — moves through this state machine. Short-running calls skip straight from COMMITTED to SETTLED.

  1. SUBMITTINGLocal — wallet interaction, transaction not yet sent.
  2. PENDING_COMMITMENTTransaction sent, awaiting executor commitment.
  3. COMMITTEDJobAdded event fired — an executor has claimed the job.
  4. EXECUTOR_PROCESSINGExecutor is running the work inside a TEE.
  5. RESULT_READYLong-running only: Phase 1 settled, task ID assigned.
  6. PENDING_SETTLEMENTAwaiting the Phase 2 delivery callback.
  7. SETTLEDFinal result delivered and stored on-chain. ✔
  8. FAILEDExecutor error, delivery failure, or callback revert.
  9. EXPIREDTTL passed with no settlement — cleaned up.

TEEServiceRegistry

Concept / reference0x9644…7F· reference only

The on-chain directory of registered TEE executors and their attestations. Contracts query it by capability (HTTP, LLM, image, …) to select an executor at call time — never hardcoded, so requests survive executor churn and restarts.