Jez ritual/acc (❖,❖)

Ritual Wishes on Eid Mubarak Everyone!.

Your brain might stop braining after this, but at least we'll have fun.🤭 Pull up to Guess the Gibberish in @ritualnet later and test how fast your brain catches the vibe 🧠⚡ With my co-host @NFTiyahh Later 2 PM UTC Come through 👀

If your contract needs a bot to stay alive, is it really autonomous? Ritual Scheduler fixes that Check docs.ritualfoundation.org @ritualnet @ritualfnd

⚡ Tonight, Josh and Stefan are bringing Frankenstein to life. Join the FRANKENSTEIN VIBE CODING SESSION with @joshsimenhoff and @0xMadScientist 🔥 📅 May 27, 2026 🕙 10:00 PM 🎧 Live on Discord See you there. 😊 @ritualnet

I feel the need to speak up on this because I am still seeing a significant misunderstanding around what true BRAND ALIGNMENT means when creating content for @ritualnet. Respecting a brand goes far beyond simply mentioning the project name. It involves maintaining consistency across every element: • Visual identity • Logo implementation • Color palette and design language • Overall communication style Moving away from the official brand direction, even within a single post can weaken content quality and potentially influence how future contributions are evaluated. Ritual is establishing a distinctive and high-quality brand image, and that image deserves consistency, attention to detail, and proper execution. My advice to everyone: Take some time to review your existing content and remove anything that does not align with the project’s official guidelines. Creating strong content is not only about visibility, it is about delivering the right message while preserving the integrity of the brand. Ritual Brand Kit: marshy-ermine-6e0.notion.site/Brand-Kit-2888…

Here’s this week’s Ritual Research Digest, a newsletter covering the latest in the world of LLMs and the intersection of Crypto x AI. With hundreds of papers published weekly, staying current with the latest is impossible. We do the reading so you don’t have to.

Start a new great week with Ritual! Calendar of fun and active events for this week

Congratulations to @ritualnet and to all the amazing builders 🙌 Excited to see more ideas and innovations from the community. Good vibes and good future ahead for everyone building here. The future looks exciting for this community 💚 #BuiltonRitual

Happy 1 month anniversary to Ritual Testnet ❤️ Crazy to think how much happened in just 30 days. Explored what onchain AI can become, guided new builders, created cards, experimented with SocialFi, games, artist archives, and watched ideas turn into real products. What stood out most wasn’t the tech it was the people. The builders shipping. The community helping. The endless experimenting. Feels like we’re still at day one. More agents. More apps. More weird ideas becoming reality. More things no one thought possible. Excited for what comes next. @ritualnet @ritualfnd

Ritual Testnet Stats: Week 5 Let’s look at Ritual through the numbers again. This time, the context matters. Week 1 looked like the HTTP week. The main question was simple: can contracts reach outside the chain? HTTP was the obvious primitive to test first because it is easy to understand, easy to call, and easy to build around. Week 2 became more agent-shaped. Sovereign Agent started moving up, and the signal changed. Builders were not only asking for data anymore. They were starting to test agents as execution primitives. Week 3 looked more balanced. HTTP, Long-Running HTTP, Sovereign Agent, DKMS, LLM, and media calls started to look like parts of one stack. That was the first week where Ritual activity felt less like one feature winning and more like builders climbing the stack. Week 4 made the async layer harder to ignore. Sovereign Agent led again, but the bigger story was transaction flow: async commitments, async settlements, and scheduled execution started taking most of the window. So Week 4 was not just agents are active. It was: agents are active inside async workflows. Now Week 5 matters because the pattern did not disappear. It repeated. EIP-1559 is still the biggest single transaction category at 32.93%. That is normal. Builders still need regular EVM activity. They deploy contracts, call functions, test interfaces, and move through the usual development loop. But regular EVM activity is only about one third of this window. The other two thirds are scheduled and async transactions. Scheduled is 15.37%. Async Commitment is 20.16%. Async Settlement is 31.54%. That changes how I read the network. This does not look like a testnet where people only send simple calls and click buttons. It looks like work is already moving through phases. A scheduled transaction means something is meant to happen later. An async commitment means work entered an execution flow. An async settlement means a result came back and had to be settled. So the basic unit is no longer only transaction. It starts to look like workflow. The precompile stats make that clearer. Sovereign Agent leads again at 31.4%. HTTP Call follows at 27.5%. Long-Running HTTP is third at 15.7%. That is almost the same shape that started becoming visible in Week 4. Agents first. External context close behind. Longer tasks underneath. That is the important part. If this were only AI hype, I would expect LLM calls to dominate. They do not. LLM Call is at 8.8%. Instead, the dominant pattern is agent, external context, longer task, async lifecycle, scheduled return. That is much more useful than saying people are using AI. An agent without context is weak. It can answer, but it is mostly trapped inside a prompt. HTTP gives it the outside world. Long-Running HTTP gives it room for work that does not fit into one instant response. Async Commitment and Settlement give that work a lifecycle. Scheduler gives it time. This is the thread across the last few weeks. Week 1 asked: can contracts see outside? Week 2 asked: can agents become a real primitive? Week 3 asked: can these primitives start forming a stack? Week 4 asked: can async execution become the rhythm? Week 5 is starting to answer: yes, this pattern is repeating. The autonomous agents page adds another layer: 58 agents registered, with 33 Persistent and 25 Sovereign. That matters because the Sovereign Agent precompile number is not floating alone. There is already an agent surface forming. Persistent agents point toward longer-lived identity and state. Sovereign agents point toward execution participants. The base layer is active too: 37 validators, 37 active proposers, and 532 blocks analyzed in the last two minutes. I would not treat short live chart windows as final benchmark numbers. They move quickly. But they do show rhythm: blocks moving, gas usage changing, block sizes shifting, and execution that is not flat. The mempool snapshot also helps. Pending transactions are low. The scheduled pool is empty. The async pipeline shows 13. That async pipeline matters for product design. If Ritual apps use async workflows, users cannot be left staring at loading. They need to know where the work is: submitted, committed, settled, delivered, expired, or failed. A normal dApp can often pretend everything is one transaction. A Ritual app cannot. The workflow itself has to be visible. So Week 5 is not a totally new story. That is exactly why it matters. The same pattern keeps showing up. Transaction types show scheduled and async activity making up most of the window. Precompiles show Sovereign Agent, HTTP, and Long-Running HTTP leading. Agent stats show registered Persistent and Sovereign agents. Validator stats show live base-layer activity. Mempool shows not only pending transactions, but an async pipeline. The conclusion is pretty clear. Ritual testnet is not only being used as an EVM chain. It is being tested as a workflow environment. That is the important distinction. A normal chain is mostly about transactions. Ritual is starting to show another pattern: transactions start work, agents add execution, HTTP adds context, long-running calls add time, Scheduler brings work back later, async commitment and settlement give the process a lifecycle, and DKMS prepares the access layer. This is still early. The windows are small. The numbers can move quickly. But as a Week 5 signal, it is meaningful. Not because one metric exploded. Because the pattern survived another week. Not only transactions. Workflow behavior. Check: explorer.ritualfoundation.org/stats @ritualnet @ritualfnd

I got into crypto for one reason: don't trust, verify. Then AI showed up and we all just... trusted the black box owned by 5 companies. @ritualnet is the first project that felt like it actually cares about fixing that contradiction.

Ritual Community are you all ready? 💯🔥 Finally we are back on another new exciting journey within the Ritual community 🥳 Featuring ╰┈➤ Host: @YeaItsHeat @Intuitionweb3 Speakers: @Evoyudhasamael @Oluwasegun1334 @AbrahamJT9 @kaicrypt00 @jepslife See you all there! 💚🥳

🧟‍♂️ Frankenstein VIBE CODING SESSION 🧟‍♂️ with @joshsimenhoff and @0xMadScientist The lab is open. The sparks are flying. The code is unstable. Join us for a gloriously Ritualized and unhinged vibecoding session where we'll build something on Ritual Chain live, messy, and completely experimental. 🗓️ May 27, at 10:00 PM UTC on Discord

gRitual, it's that time of the week again and we're back with the 51st episode of the weekly ritual hangout as usual, we'll be talking about all the interesting developments in the @ritualnet community with all the regional leads co-hosts: -> @ZhugeLyang kindly set a reminder👇🏽

Ritual Stats: Week 4 Week 4 feels like the agent week again. But this time the story is stronger than “Sovereign Agent is on top.” Sovereign Agent leads the precompile table with 29.5%. HTTP Call is close behind at 26.5%. Long-Running HTTP follows at 15.8%. That already says a lot. Builders are not only testing whether contracts can reach outside the chain anymore. They are moving toward the bigger question: can agents actually execute inside the workflow? That is the shift. HTTP still matters because agents need context. Long-Running HTTP still matters because real tasks take time. But Sovereign Agent on top means builders are now touching the primitive that makes Ritual feel different. The transaction types make the pattern clearer. EIP-1559 is 36.10%, so normal EVM activity is still there. Contracts are being deployed, functions are being called, and interfaces are being tested. But the rest of the window is where the Ritual-specific behavior shows up. Scheduled is 10.66%. Async Commitment is 21.13%. Async Settlement is 32.11%. Together, scheduled and async activity make up around 63.9% of this window. That is the real Week 4 signal. More than half the activity is not just regular transactions. It is jobs, commitments, settlements, scheduled execution, and results coming back later. A normal transaction is a moment. An async workflow is a process. Week 1 was mostly about external data. Week 2 showed agents starting to matter. Week 3 looked like builders were climbing the stack: HTTP, Long-Running HTTP, Sovereign Agent, DKMS, LLM, media, ZK. Week 4 feels like those pieces are starting to behave more like a system. Sovereign Agent leads. HTTP stays close. Long-Running HTTP keeps the time layer visible. LLM and DKMS both show real usage. ZK, audio, video, and FHE are still smaller, but present at the edge. That is a healthy testnet pattern. Not every primitive needs to dominate immediately. Some primitives first appear as small signals before they become normal. The thing I like most here is not one number. This does not look like random clicking. It looks like builders testing how work actually moves through Ritual. Workflow behavior. Check: explorer.ritualfoundation.org/stats @ritualnet @ritualfnd

Here’s this week’s Ritual Research Digest, a newsletter covering the latest in the world of LLMs and the intersection of Crypto x AI. With hundreds of papers published weekly, staying current with the latest is impossible. We do the reading so you don’t have to.

Ritual Continuously to Gain Movements. X consistently selects artistic endeavors and ritual builders. @nikitabier

"on-chain ai" is a meme on every chain except one. @ritualnet has 16 enshrined precompiles for it llm, zk, fhe, image, video, agents all settled inside one tx. i shipped the visual playground for every single one. 🜂 sigil-ritual.auranode.xyz

Ritualized #30 with @ritualnet 🥳 30 weeks of showing up consistently, learning, supporting, and growing the Ritual ecosystem in my own way. I'm so proud of this milestone. 😊 ✓ Catch up on the world of crypto × AI x.com/i/status/20538… ✓ @Jez_Cryptoz talking Ritual humanoid agents?! I'm sattt! 🔥 ✓ @ericgudboy says it's time to showcase the diverse possibilities on Ritual and I couldn't agree more. x.com/i/status/20551… ✓ Three weeks in, 56 amazing dApps and counting! 💪🏽 ✓ Aotw: @batagor ❤️ x.com/i/status/20551… on the road to #40! Stay updated and Ritualized. ❖