The Ritual Foundation is dedicated to the development, growth, and decentralization of the Ritual Chain @ritualnet and its ecosystem.
Joined October 2023
- Tweets421
- Following1
- Followers36.1K
- Likes75
Pinned Tweet
Ritual testnet is now live. The first chain where an agent's existence doesn't end when its creators do.
Every agent wallet leak this year looked the same: the private key was somewhere the agent could read it.
On Ritual keys stay in the enclave. It never enters the agent's context, so your harness, the model, and MCP servers never touch sensitive data and your wallet stays yours.
Today’s topic for DevRel Office Hours is the “The Empty Path” 🧵
2 weeks ago we gave builders one piece of homework: test what happens when nothing comes back. Today it comes due, and the Verify Challenge closes with it.
We also close the loop on the checks themselves.
A check flagged something that was not a real problem? A step that no longer matches the chain? Tell us. Those reports get logged on the public skills repo and shape the next version.
Today. 3:30 PM CT. Live on the Ritual Discord.
Bring your test, your callback, or just your questions.
RSVP so you get the reminder: luma.com/devevents
In November 2023 we ran an onchain AI agent managing $30,000. We were early to onchain agents, and we’re early to agentic institutions.
This year, six papers took a first shot at building a fully agentic company. All six did it offchain, by hand.
If you strip them down, the same four requirements keep showing up: an identity the agent owns, memory that outlives the process, a budget that can actually run out, and work a third party can verify.
On Ritual, all four are native to the chain.
Let the Ritual begin.
Four questions every Ritual callback should ask. 🧵
When your contract asks an AI model or a service for something, the answer comes back later. At Office Hours we drew the whole lesson as one picture: every answer, or non-answer, takes the same walk. Here it is.
The rule of thumb: every "no" ends in a state your user can see.
Timed out, rejected, failed: all fine. A silent hang where the app spins forever is the bug. An empty result is usually something on your side of the counter, not a broken executor.
Homework is due Thursday: one test where the result comes back empty or late, and a contract that handles it.
Bring it to Office Hours, Thursday, October 15 at 3:30 PM CT on Discord. Paste your callback and we will walk the four questions together. discord.gg/ritual-net
Six builder best practices for async results on Ritual 🧵
Your contract can call AI models and other services asynchronously. These habits help your dApp handle every outcomes smoothly: a result, an error, or no answer in time. Each one comes from the public Ritual skills.
Test the edges with mocks, and the full path once for real.
Use vm.mockCall to feed your contract an empty result, an error response, and an expired job. Then run one live transaction end to end, and note which results came from mocks and which came from the chain.
Want to go deeper?
These practices come straight from the public Ritual skills, and we walked through them at last week's Office Hours. The next session is Thursday, October 15 at 3:30 PM CT.
Bring your questions.
skills.ritualfoundation.org
