Olivia
Online
KINGERI.ETH (❖,❖)
@kingeri_eth
Joined June 2021
2.6K Following
1.9K Followers
939 Posts
The year is 2026. Some chains are still mastering TPS no Jutsu.
Meanwhile @ritualnet users have unlocked: 🌀 AI Agent no Jutsu
A forbidden technique that allows smart contracts to summon intelligence directly from the blockchain. S-Rank technique.
Other ninja summon frogs.
Other chains move tokens.
Ritual summons AI agents directly from smart contracts. We are not practicing the same jutsu.
Attention! Not recommended for ordinary shinobi. For them, there is a typical vanilla blockchain.
For everyone else - Ritual. Find out more:
▶️ https://t.co/ymKQMKUnw3
▶️ https://t.co/WriLqC2JiZ
▶️ https://t.co/q8fLiczbbH
Everyone is focused on AI. Almost nobody is focused on the gap.
The gap between: Thinking -> Acting
That's where front-runs happen. That's where MEV happens. That's where protocols get exploited.
Most AI systems think first and act later. @ritualnet removes the gap. Inference and execution settle as a single operation.
✨Atomic intelligence
https://t.co/mttG3diPLi
@prmakk @ritualnet @Jez_Cryptoz @joshsimenhoff @dunken9718 Yes, it's possible. But the market isn't the best right now. You might need to wait a little.
One of the weird things about crypto is that we've become completely numb to technological progress.
A few years ago, we were excited because smart contracts could move tokens.
Today, we're casually discussing AI agents, trusted execution environments, autonomous applications, and contracts that can reason about information.
Read that again. A smart contract can call AI.
Not through a backend.
Not through someone's hidden server.
Not through "trust me bro" infrastructure.
The contract asks.
The model runs inside a TEE.
The result is verified.
The response comes back onchain.
And somehow we've reached the point where the correct reaction is: "Yeah, okay. Cool."
The Ritual cat gets it. Everyone else sees a coconut. He sees the future of programmable intelligence.
Welcome to @ritualnet.
One of the things I like most about @ritualnet is that it's a surprisingly serious project surrounded by surprisingly unserious people.
On one side, you have developers figuring out how to run AI, building new infrastructure, experimenting with agent architectures and trying to push crypto beyond simple token transfers.
On the other side, you have a community that somehow decided a black cat is an acceptable representation of all of this.
And honestly? That feels right.
Crypto has always been at its best when ambitious technology meets internet culture.
The technology matters.
The research matters.
The builders matter.
But if you can't occasionally step away from the terminal, sit on a beach, and laugh at how ridiculous this industry can be, you're probably doing it wrong.
So here's to the builders shipping through the summer.
The researchers cooking in the background.
The agents doing their thing.
And the Ritual cats staying completely unbothered.
☀️🐈🤖
Summer with @ritualnet!
💣@ritualnet is EVM-compatible. But it's not just EVM.
Regular EVM gives you a ledger that executes code. That's it.
Ritual adds things that are simply impossible on vanilla EVM:
🔸AI inference as a native precompile. One line from your contract. Result comes back verified. No external API, no trust required.
🔸Native Scheduler. Your contract runs on a schedule. No Chainlink Keepers, no Gelato. The block proposer handles it at the protocol level.
🔸Agents that never stop. Own wallet, own gas, self-restarting. Enforced by the chain itself - not approximated by a Solidity library.
🔸Verifiable computation. Every AI output comes with a ZK or TEE proof. Anyone can verify. No one needs to trust anyone.
That's what "native" actually means.
@ritualdigest Excellent digest! Thank you!
Our typical summer @ritualnet checklist:
☀️ Touch the grass
🌊 Touch the water
🐈 Touch the cat
🔁 Repeat
But this does not prevent us from participating in the testnet, which is already in full swing. We already have more than 50 dapps and new ones are appearing every day.
Summer is a time of change. Perhaps the main network? Perhaps...
The AI narrative isn't about smarter models anymore. It's about who controls them.
Most AI apps still require you to trust: provider, API, infrastructure, operator.
@ritualnet changes the trust model itself:
✅Private inference.
✅TEE verification.
✅Onchain execution.
✅Not "trust me bro" AI.
✅Verifiable AI.
That's the alpha.
Private money: 15-year thesis, soft conversion.
Private AI: 3M+ users in a quarter.
The bottleneck on both is the same — a substrate that doesn't require trusting the operator. Ritual Chain is built for the second category, where the demand is already proven.
The crypto market changes insanely fast. Not that long ago, we were building smart contracts and thought it was pure magic.
Today, @ritualnet lets smart contracts call AI.
Which led me to this completely scientific timeline:
✅Crypto 2021: "wen moon?"
✅Crypto 2024: "AI AI AI"
➡️Crypto 2026: "bro my smart contract has opinions"
We are creating Frankenstein with the @ritualnet right now.
A very exciting and fun process! This clearly shows that developing a DAPP for the Ritual ecosystem is limited only by your imagination.
Most AI+crypto projects follow the same playbook. But not @ritualnet.
The typical flow looks something like this:
1. Take a blockchain.
2. Plug in an LLM API.
3. Call it AI-powered.
4. Ship a landing page.
The result: AI lives on a centralized server. The blockchain just stores the output. You trust the provider. Nothing is verified. The "agent" dies when someone forgets to pay the AWS bill.
Ritual does something structurally different. Inference happens off-chain, but the result comes back on-chain with a cryptographic proof. Nobody trusts anyone. The output is verifiable.
The agent has its own wallet. Pays its own gas. Restarts itself. Calls the model before every decision.
This isn't AI on top of crypto anymore. It’s AI inside crypto.
Ritual is building real infrastructure. And in 3 years the difference will be obvious.
The hardest parts of building a dApp on @ritualnet. Honestly.
_receiveCompute(). Looks simple until it doesn't fire. It's an internal override with 9 parameters (subscriptionId, interval, redundancy, node, input, output, proof, containerId, index). Miss one or get the modifier wrong and nothing comes back. Check node logs first.
Thinking in async. You call _requestCompute() and nothing happens immediately. The result comes back later via callback. If you're used to synchronous code - this takes time to click.
abi.encode on the input, abi.decode on the output. Get the types wrong once and you'll spend an hour on it.
Container IDs. You're not calling a model directly - you're calling a container that runs the model. Small distinction, big confusion at first.
None of this is insurmountable. Docs are solid. Community helps fast.
But it's definitely not plug and play. That's also what makes it interesting.
Every project has its stars. And the @ritualnet was no exception. People look at them, imitate them, and many want to be like them.
The CIS community has its own star. Unique, cool, and committed to the project's values.
Touch @meison_mswen >>> Touch grass
Most Popular Users
Elon Musk
@elonmusk
240.1M followers
Barack Obama
@barackobama
119.3M followers
Donald J. Trump
@realdonaldtrump
111.6M followers
Cristiano Ronaldo
@cristiano
108.8M followers
Narendra Modi
@narendramodi
106.9M followers
Rihanna
@rihanna
97.2M followers
NASA
@nasa
92.1M followers
Justin Bieber
@justinbieber
90.5M followers
KATY PERRY
@katyperry
86.7M followers
Taylor Swift
@taylorswift13
80.5M followers
Lady Gaga
@ladygaga
72.1M followers
Kim Kardashian
@kimkardashian
69.3M followers
YouTube
@youtube
68.6M followers
Virat Kohli
@imvkohli
68.4M followers
Bill Gates
@billgates
63.4M followers
The Ellen Show
@theellenshow
62.5M followers
CNN
@cnn
61.9M followers
Neymar Jr
@neymarjr
61M followers
X
@x
60.9M followers
CNN Breaking News
@cnnbrk
59.9M followers