Unofficial Ritual testnet builder campaign

Mission Console

A guided builder campaign for trying Ritual primitives step by step: wallet setup, async fees, HTTP, LLM, SecretsACL, proof reads, and completion NFT minting.

Build v25

Not connected

Made by HB (@herbcase7)

How to use this

Complete the missions in order

Each button creates either a real testnet transaction or a read-only verification. Keep the Activity panel visible while you work; it shows transaction hashes, errors, and what to check in the explorer.

Set up wallet and confirm you are on Ritual Chain.
Fund RitualWallet so async executors can settle HTTP and LLM work.
Run primitive tests with a public HTTP endpoint and a short LLM prompt.
Create a SecretsACL proof by deploying a proof contract and granting access.
Mint a completion NFT with your proof, PFP, nickname, and X handle.

Wallet Setup

Connect and inspect chain state

Connect your wallet, switch to Ritual testnet, then refresh to discover active HTTP and LLM executors. Your wallet address is the identity used for transactions and proof records.

This console works best with MetaMask and OKX Wallet. Rabby Wallet may fail on Ritual testnet because its pre-transaction simulation is not currently compatible with the Ritual RPC.

Account -

RitualWallet balance -

Lock until block -

HTTP executor -

LLM executor -

Current block -

Async Fee Account

Fund RitualWallet

RitualWallet is not a separate browser wallet. It is an on-chain fee account used by Ritual executors. Normal gas pays the transaction, while this deposit pays async executor work such as HTTP or LLM settlement.

Amount Start small. Simple HTTP tests usually need little balance; LLM calls may use more. Lock blocks Funds are available for executor fees until this future block window passes.

Primitive Tests

Run HTTP and LLM executor calls

This step proves the core Ritual idea: your transaction can request off-chain work from an executor, then bring the result back to the chain.

3-1. HTTP

Fetch a public API

The HTTP precompile asks a TEE executor to call a public URL and settle the result on-chain.

Requires Step 2. If RitualWallet is not funded and locked long enough, the executor will reject the async payload.

URL Use a public endpoint. Do not paste API keys here. TTL blocks How long this request may stay valid for execution.

3-2. LLM

Send a short prompt

The LLM precompile routes a prompt through Ritual's model executor path.

Requires Step 2. LLM calls usually need more RitualWallet fee balance than a small HTTP ping.

Prompt Write any prompt you want. Start short because longer prompts can increase executor fee usage. TTL blocks LLM settlement can take longer than an HTTP ping.

SecretsACL Proof

Deploy, grant, check, and record access

SecretsACL is an on-chain permission table. This mission deploys a small proof contract, generates a test secretsHash, grants that contract access, and records the access result.

Delegate is the proof contract that receives permission.

Secrets hash is a bytes32 identifier for an encrypted secret, not the secret itself.

Expires at block is the block when permission should stop working.

Deployed proof contract -

Generated secrets hash -

Delegate The deployed proof contract address. You can also paste another delegate manually. Secrets hash Must be 0x plus 64 hex characters. Expires at block Use a future block. Current block is visible in Step 1. Owner for check Leave empty to use your connected wallet as owner.

Access result -

Verify and Claim NFT

Read proofs and mint a completion NFT

Read public proof variables for screenshots, then preview the completion NFT. Upload metadata to IPFS and mint an on-chain Mission Pass when the proof is complete.

Proof contract Auto-filled after deploying a Secrets proof. Scheduler proof addresses can be pasted manually. Proof type Secrets checks ACL. Scheduler checks automatic execution counters.

Mission NFT collection Not configured

Nickname This text is centered inside the silver name plate on the NFT image. X handle This text is centered inside the lower gray plate. X PFP auto-fetch needs OAuth/server support, so use image upload for now. Upload PFP image The image stays in your browser until Claim NFT uploads the final PNG metadata to IPFS.

Advanced Cleanup

Revoke access after you finish

Revoke Access removes the delegate's permission for the selected secrets hash. Use this after taking screenshots or finishing the mission if you want to keep your wallet's delegated permissions tidy.

If you revoke before recording or reading your proof, live access checks will return false. This is a cleanup action, not a required campaign step.

Activity

Watch this while completing missions. Use explorer links to confirm status, destination contracts, logs, and block numbers.

Ready.