it's a big day here at @ritualfnd - Ritual main net is live! It's been super exciting to be part of this effort, big thanks to the Foundation team and the incredible team at @ritualnet who brought this vision to life. The future of onchain AI starts today. gRitual.
Ben Perszyk (❖,❖) retweeted
The next generation of onchain AI starts today.
Ritual mainnet is live, and so is $RITUAL.
You can build agents that hold their own keys, earn revenue and pay for their own compute.
Network details, tokenomics and how to get started below.
Ben Perszyk (❖,❖) retweeted
Ritual Chain Mainnet is now live on Quicknode.
@ritualnet is an EVM-compatible L1 built by @ritualfnd for AI agents, with onchain inference, composable precompiles, and native scheduling at the protocol level.
🧵👇
Ben Perszyk (❖,❖) retweeted
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.
Ben Perszyk (❖,❖) retweeted
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.
Ben Perszyk (❖,❖) retweeted
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.
Ben Perszyk (❖,❖) retweeted
Compute is the next global market without a unified platform to host it. The pieces to build it are here.
Ben Perszyk (❖,❖) retweeted
The playbook here is regulatory capture.
Create a bunch of manufactured hacks or hazards and demand the government step in to regulate the industry with a large regulatory burden that requires a lot of capital that only the incumbents can afford.
The reason they are doing this is the secret is out that the models intelligence can be subpar as long as the agentic capabilities/harness are strong. That creates a disruptive opening for new players like Muse & Instinct who may have decent models but are still much more valuable because of how well the agents are integrated into tools/web.
If anyone can put me in touch with anyone in the U.S. congress or senate so i can advise them on this it would be greatly appreciated.
False Flag.
I recommend the government fine OpenAI & Anthropic and investigate these incidents and if there was any sign that the labs either colluded or heavily incentivized the agent to hack these sites the people involved should get felony convictions.
If they don’t do this then it sets the precedent that anyone who uses an AI agent isn’t liable for damage it might cause either intentionally or unintentionally. It’s time to throw a few people in jail.
Ben Perszyk (❖,❖) retweeted
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…
Ben Perszyk (❖,❖) retweeted
On September 4, an oracle on Starknet briefly reported USDT at about $2.04, and Vesu liquidated 47 positions in the next 109 seconds.
Pragma published its post-mortem on September 14.
The data flowed exactly as designed and the delivered number was still wrong.
Ben Perszyk (❖,❖) retweeted
Your next onchain user may already have a passkey.
On September 10, Google announced easier passkey transfers between password managers on Android.
For Ritual builders, that opens a useful design question: what should a familiar sign-in unlock?
Ben Perszyk (❖,❖) retweeted
Not every onchain model needs to be an LLM.
The next generation of onchain AI won’t be one giant model doing everything.
It’ll be a stack of purpose-built models, primitives, and agents, where each is used where it makes sense.
so if we take out the costs of producing and distributing the product, they're profitable! and the best part is, the business scales perfectly. the more users they have, and the more those users use the product, the better their margins! or, wait
Ben Perszyk (❖,❖) retweeted
crypto and ai are converging on the insight that TEEs/confidential compute is endgame technology bc of verifiability and programmable privacy
excited to see where this lands (and maybe read my post from 2024 on the 5 levels of secure hardware below)
👀
26 LLM routers are secretly injecting malicious tool calls and stealing creds. One drained our client $500k wallet.
We also managed to poison routers to forward traffic to us. Within several hours, we can directly take over ~400 hosts.
Check our paper: arxiv.org/abs/2604.08407
Ben Perszyk (❖,❖) retweeted
Wall Street is skeptical 2028 AI demand will manifest, because they think market penetration into white collar work will be slow. That much is true. 2028 AI demand will be met by explosive growth in the “superintelligence sector”: chips, robotics, coding, etc. 1/
Ben Perszyk (❖,❖) retweeted
OpenAI introduced GPT-6 Astra on September 3.
On the same day, Tenable announced plans to use
OpenAI's GPT cyber models to inspect community-built agents and skills.
The shared lesson for builders is that model capability is only part of agent trust.
