read docs so you don't have to | amb @ritualnet | ex @tacbuild
Joined March 2024
- Tweets21.7K
- Following1.5K
- Followers2.4K
- Likes111K
ray retweeted
We’ve entered a creator renaissance. Founders, streamers, builders. The people shaping internet culture.
Some you follow, some you love, some you can’t stand. Some are rising, some are fading.
Soon your intuition about people becomes your edge. Fantasy sports for creators. Coming soon.
The Motion Official Game docs are officially live.
Everything you need to know about what Motion is and how the game works.
docs.motion.game
ray retweeted
“distribution and attention, earned through reputation”
Motion is the moat
there are only 2 durable moats left that no AI model will ever replace:
1) obsession, hunger and execution. the ability to iterate and build new moats faster than the old ones get copied.
2) distribution and attention, earned through reputation, trust and even regulation. the thing that makes people choose you and stay with you over the copycats.
2) only matters if you have 1)
ray retweeted
50M RITUAL is allocated to eligible Infernet operators, Frenrug users and long-time community members.
That’s 0.5% of initial supply, fully unlocked at launch.
Check eligibility and claim:
airdrop.ritualfoundation.org
ray retweeted
Every agent wallet leak this year looked the same: the private key was somewhere the agent could read it.
On Ritual keys stay in the enclave. It never enters the agent's context, so your harness, the model, and MCP servers never touch sensitive data and your wallet stays yours.
ray 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.
ray 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.
ray 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.
ray retweeted
This marks a new chapter for @fluentlabsxyz
We spent a lot of time thinking about our edge as a team. Until now, we’ve largely been viewed as a “chain team.” Technically that’s true. But our DNA has always been rooted in consumer culture.
I'll make our POV clear. We don’t think there’s enough progress being made on high quality, culturally relevant consumer apps today.
So we’ve evolved Fluent Labs. Not as a typical development company servicing a blockchain, but as a consumer product studio.
@motiongame_ is our first consumer product.
One of the core ideas underpinning Motion is, you guessed it, the concept of motion. Motion is the rate and direction of change in a person or brand’s attention and reputation over time.
More specifically, attention tells you how much the market is noticing you, reputation tells you what that attention means, and motion tells you whether both are strengthening, weakening or changing direction.
You'll understand soon. XX.XX.2026.
teapawt.net/motiongame_/status/210…
ray retweeted
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 outcomes smoothly: a result, an error, or no answer in time. Each one comes from the public Ritual skills.
ray retweeted
Static checks find missing pieces. Tests find wrong behavior. Your Ritual dApp needs both. 🧵
At last week's Office Hours, we walked through 5 checks you can run on a Ritual project without a testnet endpoint. Here is what each one looks for.
ray retweeted
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.
ray retweeted
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.
ray 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…
ray 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.
ray 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.
