Ritual DevRel Office Hours is today: What the Checks Caught 🧵 2 weeks ago, we asked builders to run 5 verification checks on their Ritual project: find one bug, fix it, and share the before and after. Today at 3:30 PM CT, we look at what those checks found.

The new lesson is what to do when nothing comes back. An async call on Ritual can return a result, an error, or no answer in time. We will cover reading hasError first, sizing ttl in Ritual blocks, and mocking the empty, error, and expired cases.

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 outcome 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.

Spain's data regulator published its first breach report tied to an AI agent on September 15. It named no company, product, or cause. It named where to look: prompts, logs, conversation histories, agent memory. Memory is now a reportable surface.  cypro.co.uk/insights/cyber-b…

A pointer is not a promise. An immutable reference keeps nothing alive, and deleting one copy does not clear every replica. Ritual lets you decide who can read the path, how long it is kept, and what your contract does when a fetch returns nothing. That failure settles with hasError true.