# Ritual mainnet goes live with delegated AI execution for EVM contracts

Canonical: https://forkbrief.com/news/609d4b4b-7b9b-4880-b4f9-bccdcc45ff80
Published: 2026-10-27T10:49:00.680Z
Publisher: Fork Brief

Ritual’s October 26 mainnet announcement comes with documented EVM integration paths for delegated AI and HTTP work, including a one-async-call constraint.

The Ritual Foundation announced that Ritual mainnet went live on October 26, moving the project beyond its public testnet. Its launch announcement describes a purpose-built blockchain for applications that combine persistent identity, AI inference and settlement. For developers, the concrete change is a live network accompanied by documentation for accessing external computation through EVM contracts.

The [developer documentation](https://docs.ritualfoundation.org/) checked on October 27 identifies Ritual Chain as chain ID 784 and publishes its RPC and explorer addresses. It describes two execution paths sharing the same state. Validators repeat deterministic EVM operations such as transfers and contract storage changes. AI inference, HTTP requests and other delegated workloads run in a trusted execution environment, with the resulting computation returned to the chain.

That design gives contract developers a protocol interface for requesting external work. It also introduces an execution lifecycle that applications have to handle. Short asynchronous calls return their results through the originating transaction's processing path. Longer jobs commit a request first and deliver the result through a later callback transaction.

One documented constraint matters for application design: a transaction can contain only one asynchronous precompile call. An application combining an HTTP request with an AI inference request therefore needs separate transactions or scheduling, rather than placing both asynchronous calls in one transaction. The documentation also tells developers to check that a callback's preconditions still hold, because shared contract state can change while a job is pending.

The [Foundation's October 26 announcement](https://www.ritualfoundation.org/blog/ritual-mainnet-is-live) marks the move to mainnet. The integration rules are documented behavior, and the launch announcement does not establish how widely production applications have adopted those interfaces.

## Sources

- [Ritual Chain Developer Documentation](https://docs.ritualfoundation.org/) — Ritual Foundation
- [Ritual Mainnet is Live](https://www.ritualfoundation.org/blog/ritual-mainnet-is-live) — Ritual Foundation

- [Editorial policy](https://forkbrief.com/editorial-policy)
- [Request a correction](https://forkbrief.com/corrections)