Ritual has been one of the most-watched names in crypto AI since it came out of stealth in late 2023, yet for most of that time there was little an ordinary user could touch. That changed in June 2026, when the Ritual Foundation opened a public testnet for Ritual Chain, with a faucet, an explorer and a public RPC. This guide explains what Ritual Chain is, what you can actually do on the testnet, why the testnet RITUAL in your wallet is not an airdrop, and how to use the network without walking into the scams that always follow a high-profile launch.
Ritual in one paragraph
Ritual’s pitch is a blockchain where smart contracts can call AI models and the outside world natively, rather than through a patchwork of oracles and off-chain bots. The project emerged in November 2023 with a $25 million Series A led by Archetype and an early product called Infernet, a decentralized oracle network that let contracts on existing chains request AI inference. It followed with Frenrug, an on-chain AI agent on Base, open-source tooling such as infernet-ml, and an ecosystem programme called Altar. A private Ritual Chain testnet was unveiled at the end of 2024, alongside the creation of the Ritual Foundation, which now maintains the chain’s documentation and runs the public testnet.
What makes Ritual Chain different
Ritual Chain is EVM-compatible, so Solidity contracts and standard wallets work. The differences sit underneath:
- Native precompiles instead of Infernet. The current docs state that Ritual Chain replaces the Infernet protocol with built-in precompiles, and tell existing Infernet integrations to migrate. The precompile map covers HTTP requests, LLM inference, classical ONNX models, JQ queries, signature verification, distributed key management (DKMS), secrets, ZK proofs, FHE inference, multimodal generation and agents.
- Verified off-chain execution. Heavy work runs in trusted execution environments, and results are cryptographically tied to the request that triggered them. The docs describe a “superposition” model where ordinary EVM execution (re-run by every validator) and delegated execution (run once in a TEE and verified) share a single state.
- Native scheduling. A Scheduler system contract lets contracts run at future blocks, on a recurring basis or when a condition is met, without external keeper bots.
- Pricing for uneven workloads. Resonance, introduced in 2024, is a fee mechanism where market-makers match workloads to compute providers, because a single gas price cannot sensibly cover both a token transfer and an LLM call.
- Symphony consensus. Presented in early 2026 and published as a whitepaper in April 2026, Symphony separates block proposing from execution so that nodes with specialised hardware can take on the expensive tasks.
The team frames all of this around autonomous agents: programs that can hold funds, call web APIs, keep secrets and keep running without a human operator. The Foundation’s docs list seven properties it wants agents to have, including what it calls immortality, financial sovereignty and web2 interoperability.

The public testnet at a glance
The Ritual Foundation announced on June 23, 2026 that the Ritual Chain public testnet was live, describing it as a chain built for AI agents with on-chain inference, composable precompiles and native scheduling. The network details published in the Foundation’s docs:
| Item | Value |
|---|---|
| Chain ID | 1979 |
| Currency | RITUAL (18 decimals, testnet only) |
| Block time | Roughly 350 ms |
| RPC | rpc.ritualfoundation.org (HTTP and WebSocket) |
| Explorer | explorer.ritualfoundation.org |
| Faucet | faucet.ritualfoundation.org |
Note the domains. Developer material now lives under ritualfoundation.org, and the old docs address at docs.ritual.net redirects there. The company site remains ritual.net. Anything outside those two domains claiming to be a Ritual faucet or bridge should be treated as unofficial.
Is there a Ritual token or airdrop?
Not one that Ritual has announced. The testnet’s native currency is called RITUAL, which causes confusion, but the docs label it as a testnet currency handed out free by the faucet. It has no market value and cannot be bridged to a mainnet.
At the time of writing, Ritual has not published tokenomics, a token generation date, a points programme or any eligibility criteria for a future distribution. Its public writing in 2026 has been research: papers on verifiable LLM inference, transaction ordering, auctions with collusion, and the Symphony consensus design. Several airdrop aggregators publish “Ritual airdrop” task lists, and some quote specific allocation numbers. None of those figures come from Ritual or the Foundation, so they should be read as speculation.
That matters for how you spend time on the testnet. Use it because you want to learn or build on an AI-native chain. If a future reward programme appears, Ritual will define its own rules; nobody outside the team knows today whether testnet activity will count.
How to get started on Ritual Chain
For users
- Use a separate browser wallet with no mainnet funds. Add a custom network with chain ID 1979 and the RPC endpoint from the docs.
- Go to faucet.ritualfoundation.org, connect the wallet or paste the address, and request testnet RITUAL.
- Look up your address on explorer.ritualfoundation.org to confirm the tokens arrived. Getting used to the explorer early helps you check later transactions, including scheduled and TEE-executed calls.
- Read the “For Users” section of the docs before interacting with apps. Ritual supports passkey-based authentication and a RitualWallet contract that escrows fees for asynchronous calls, so some flows look different from a normal EVM chain.
For developers
- Start with the Quick Start and the Precompile Map in the Ritual documentation.
- Pick one precompile and build a small consumer contract: an HTTP call that pulls a price from a web API, or an LLM call that classifies text. The docs include consumer patterns for both synchronous and long-running calls.
- Fund the RitualWallet escrow for your contract so delegated tasks can pay their fees.
- Try the Scheduler to run a function every N blocks. This is where Ritual’s design is most visibly different from other EVM chains.
- If you previously built on Infernet, follow the migration notes to the equivalent precompile addresses.
The Foundation also publishes “ritual-dapp-skills”, agent-oriented build instructions, and a full whitepaper on its own domain for deeper reading.
A sensible first project
If you want one exercise that shows what is distinctive about the chain, combine three features in a single contract: a scheduled job that runs once a day, an HTTP precompile call that fetches a public data point, and an LLM precompile call that summarises or classifies the result before writing it to storage. On most EVM chains that would need an oracle, a keeper network and an off-chain server. On Ritual it is one contract plus a funded fee escrow. Watching the scheduled and delegated transactions appear in the explorer is the quickest way to understand how the superposition model behaves in practice, and it gives you something concrete to compare against other AI-focused chains.

Risks specific to Ritual right now
- Testnet resets. A public testnet can be reset or migrated. Contracts, balances and agents you deploy may not survive, so do not build anything you cannot redeploy.
- Secrets and keys on a test network. Ritual’s secrets and DKMS features invite you to hand API keys to contracts. On a testnet, use throwaway keys with tight spending limits, never production credentials.
- TEE trust assumptions. Delegated execution relies on trusted hardware attestation. That is a different security model from pure re-execution, and it is worth understanding before you rely on results for anything valuable.
- Agents with wallets. An autonomous agent that holds funds and calls external APIs can misbehave in ways a normal contract cannot. Keep agent balances to testnet tokens.
- Name confusion. Search results for “RITUAL token” may surface unrelated tokens on other chains. Ritual has not launched a tradable token, so any market listing you find is not the project’s.
How fake Ritual pages operate
A public testnet with a named currency is ideal material for scammers. Typical patterns:
- “RITUAL airdrop checker” or “claim RITUAL” sites. There is no announced claim, so every such page is unofficial.
- Fake faucets on lookalike domains that ask you to “verify” by signing a token approval on Ethereum. The real faucet is on ritualfoundation.org and only needs an address.
- Tokens named RITUAL trading on DEXs. These are not issued by Ritual.
- Impersonators of the official X accounts, @ritualnet for the company and @ritualfnd for the Foundation, or Discord “moderators” who DM first.
When in doubt, navigate to ritual.net or ritualfoundation.org directly instead of following a link from a reply or DM.
FAQ
Does the testnet RITUAL have any value?
No. It is free faucet currency for paying fees on a test network.
Is Infernet still worth learning?
For historical context, yes. For new projects, the docs point developers to Ritual Chain’s native precompiles, which replace Infernet.
Do I need special hardware to use the testnet?
Not as a user or contract developer. The TEE executors and specialised nodes are run by the network, and you interact with them through precompiles.
Has Ritual confirmed that testnet activity counts toward anything?
No. Ritual has not announced any points system, snapshot or eligibility rule tied to the public testnet.
Verdict
Ritual Chain’s public testnet is one of the more technically ambitious things you can try in crypto AI: contracts that call language models, fetch web data, keep secrets and schedule themselves. It is worth an afternoon for anyone curious about on-chain agents and worth much more for developers. It is not, at this point, an airdrop campaign. There is no announced token, no points and no snapshot, and the only RITUAL you can get is free testnet currency. Approach it as a builder’s sandbox and you will not be disappointed.
This article is for information only and is not financial advice. Testnets can change or reset without notice.
Related guides
- 0G Galileo Testnet 2026: How to Use the Portal, Faucet, and Explorer Safely
- Knidos Testnet Goes Live: How to Earn AP and Position Yourself for a Potential Future Airdrop
- Gensyn Testnet 2026: How to Use the Dashboard and Track Node Activity Safely
- OpenLedger in 2026: After the OPEN Airdrop, How Datanet Rewards Work and How to Avoid Claim Scams