Ritual Testnet Stats: Week 7 This week feels like a good moment to stop asking the easy question. The easy question is: which primitive is winning? HTTP is first at 31.9%. Sovereign Agent is second at 30.9%. Long-Running HTTP is third at 15.8%. So the lazy read would be: HTTP is back on top. But I think that misses the more interesting part. These numbers do not look like primitives competing with each other. They look like division of labor. HTTP is not beating agents. It is feeding them context. Sovereign Agent is not replacing HTTP. It is becoming the execution surface around that context. Long-Running HTTP is not just a slower API call. It is the admission that useful work often refuses to fit inside one instant response. That is the Week 7 signal for me. Ritual is starting to look less like a collection of features and more like a small economy of work. Some work needs context. Some work needs agency. Some work needs time. Some work needs settlement. Some work still needs normal EVM execution underneath. And the testnet is starting to show all of those layers moving at once. EIP-1559 is 39.05%, which means the normal EVM base is still alive and important. That is good. A chain that only shows exotic activity can be misleading. Builders still need boring transactions: deployments, contract calls, testing, state changes, basic interactions. That is the ground layer. But the rest of the activity bends away from normal EVM behavior. Scheduled is 13.82%. Async Commitment is 23.90%. Async Settlement is 23.23%. Async adoption is 47.13%. So almost half of the window is async. Not a small side experiment. Not a decorative AI layer. Almost every second transaction is part of work that has phases. A normal transaction has a simple shape: send, execute, done. Ritual keeps showing a different shape: start, wait, commit, settle, return. That shape matters more than the raw percentage. It means builders are testing time, delay, external context, and callbacks as first-class parts of applications. This is where Ritual watch awesome . Not it has AI. Many projects have AI. Ritual is i the network is slowly teaching builders to think in workflows instead of moments. The scheduled jobs number makes this clearer. Active scheduled jobs: 207. That might be one of the most important numbers this week. A scheduled job is basically a promise to the future. It says: not now, but later. That sounds simple, but most dApps are terrible at “later.” They depend on keepers, bots, servers, dashboards, scripts, or users coming back and clicking again. Ritual makes “later” part of the execution environment. For agents, that is huge. An agent that only acts when a user pokes it is not really an agent. It is a button with better branding. A useful agent needs to return, check again, wait for a condition, retry, follow up, and continue after the user leaves. So when scheduled jobs rise, I do not read it only as more automation. I read it as the beginning of persistent behavior. The network is not only processing transactions. It is holding intentions. The mempool snapshot is also very Ritual-looking. Pending transactions are at 0. Scheduled pool is at 1. Async pipeline is at 33. Base fee is 7 wei. The normal pending queue is empty. The network is not congested. But the async pipeline is alive. That tells us something subtle: the interesting work is not always visible in the place crypto users are used to watching. On a normal chain, people look at pending transactions and gas. On Ritual, you also have to look at the pipeline. That is where delayed work lives. That is where the workflow is still breathing. This is also a UX warning for builders. If you build a Ritual app like a normal dApp, you will probably make it feel broken. Normal dApp UX mostly says pending or confirmed. Ritual apps need more language: submitted, committed, polling, waiting, settling, delivered, expired, failed. The app has to explain where the work is, not only whether the transaction landed. That is not a small frontend detail. It is the difference between a user trusting the workflow and a user thinking nothing is happening. The precompile table also says something healthy about the testnet. LLM Call is only 4.7%. That surprised me in a good way. If Ritual were only attracting people who want to spam AI onchain, LLM would probably be much higher. But the top of the table is HTTP, Sovereign Agent, and Long-Running HTTP. That means builders are not only testing model calls. They are testing the plumbing around intelligence. Context. Agents. Longer external work. That is healthier. A model call is only one part of the loop. Before the model can reason, it needs context. After it reasons, something has to execute. If the task takes time, something has to wait. If the result matters, something has to settle. If access is needed, something has to handle keys and secrets. That is why DKMS at 5.7% is worth noticing too. It is not the loudest number, but it is a serious one. DKMS is the kind of primitive people ignore until they try to build something real. Then they realize agents need permissions, credentials, private access, and controlled secrets. Without that, agents stay in demo land. With it, they can start touching real workflows. So the Week 7 distribution feels more grounded than flashy. HTTP is context. Sovereign Agent is execution presence. Long-Running HTTP is patience. DKMS is access. LLM is reasoning. Async is lifecycle. Scheduler is future intent. EIP-1559 is the EVM base. That is not random activity. That is the outline of an operating environment. The agent numbers add another layer: 33 Persistent and 17 Sovereign agents. At first glance, that might look smaller than expected. But Sovereign Agent is still 30.9% of precompile usage. So the story is not only how many agents are registered. The story is how much the agent path is being used. A network can have many registered objects and no meaningful activity. Here, the agent primitive is sitting almost equal with HTTP at the top of precompile usage. That suggests the testnet is not only collecting agents. It is exercising them. The validator and block data give the base layer context. The explorer shows fast block times, low pending activity, active validators, and mixed usage moving through the same environment. I would not turn these live windows into final benchmarks. They are snapshots. They move quickly. But they show one thing clearly: the network is handling mixed activity without looking stuck. Normal transactions. Scheduled jobs. Async commitments. Async settlements. HTTP calls. Agent calls. Long-running tasks. All of that is moving inside the same environment. That matters more to me than one headline number. Week 7 is not about a single metric exploding. It is about role separation becoming visible. Earlier weeks felt like discovery. Builders were poking primitives: HTTP here, agents there, async somewhere else. Now the activity starts to look more like a system. HTTP is the sensory layer. Long-Running HTTP is patience as infrastructure. Scheduler is intent placed into the future. Async is the lifecycle of work. Agents are execution participants. EIP-1559 is still the familiar base underneath it all. That may be the most important point. Ritual does not look like it is trying to delete the normal chain model. It looks like it is extending it. Normal transactions are still the ground. Around them, another kind of application logic is forming. Logic that can see outside, wait, return, settle, use agents, handle access, and move through phases. That is why Week 7 feels meaningful. Not because the testnet is already mature. It is not. Not because the numbers are huge. They are still early. But because the pattern is becoming harder to dismiss. Ritual is not only testing whether AI can be put onchain. It is testing whether blockchains can become environments for work that does not finish instantly. That is a much bigger idea. Most real work is not instant. Markets wait for signals. Agents wait for context. Users wait for results. Apps wait for external systems. Risk engines wait for conditions. Automation waits for time. The old chain model compresses everything into one moment. Ritual is experimenting with a chain model where work can have a process. That is the deeper Week 7 signal for me. The network is not just producing blocks. It is starting to show a grammar. Context. Agency. Time. Access. Settlement. Return. If that grammar keeps developing, Ritual apps will not feel like normal dApps with AI sprinkled on top. They will feel like workflows that happen to settle onchain. And that is a interesting future. Not only transactions. The beginning of workflow-native crypto. Check: explorer.ritualfoundation.or… @ritualnet @ritualfnd

ritual is where ai stops asking for permission quote and pass it on

People have been asking what onchain AI agents are actually for. Ritual has been building the answers:

crypto × ai has many narratives my first choice? @ritualnet quote, and pass it on 🕯️

ALL members of Wen Pal Dao just secured WL for the upcoming collection PEPE EXPLORER (@PepeExplorers) by @TrystanNFT While others chase entry, the gang were already positioned early. ⚡️

VastMint Testnet Beta is live. A native NFT launchpad and marketplace for the @ritualnet ecosystem. 111 NFT supply for early supporters. First come, first served. Mint here: vastmint.site/collections

Just gave Ritualmon a try🃏 connect wallet, pull a card, and hope RNG is on your side! ended up pulling interesting 2 Bitty cards and 4 Ritty cards so far 👀 really cool seeing all the custom card designs and borders that went into it 💚 nice build by @Zegnaeth 👏 @ritualnet ritualmon.vercel.app

Every other chain gives you a fast computer. Ritual don't need another one. Quote it. Pass it on.