The long-term goal is to continue building, and not limiting OTC to a single product.
First there were desks, then launcher, then different AMMs. Goal is to continue building for what the current meta is.
Yes, that's changing very frequently, which is why most projects die, but I'm well aware of that hence "the everything protocol" going into effect.
Let's win.
3,333 clue scrolls are coming onchain
for a loot game of lost adventurers and buried secrets
where you set out on quests for treasure yet unknown
coming soon: https://t.co/dDcaCTTj1Y
The fourth token burn has been executed, taking 543,210,899 base:0xf1e9baa65d418a9025e1851dd2d37f1ad208bba3 tokens out of circulation.
This brings the total amount of tokens burned to approximately 4,000,000,000; or 4% of the total supply.
And for the curious mind, we will continue to repeat: Ratspeak is not just for radios, and it is not a radio-only mesh network.
It’s a full heterogenous mesh - use WiFi, 5G, Bluetooth, whatever works for you.
Endless capabilities.
here is my short pitch on base:0xf1e9baa65d418a9025e1851dd2d37f1ad208bba3
most people are pricing this as an encrypted chat coin
@ratspeakorg is a transport-agnostic encrypted mesh with an app layer on top. the network underneath is reticulum: cryptographic identities, no accounts, no phone numbers, no dns, no required cloud. packets hop over lora, bluetooth, wifi, tcp, i2p, whatever can move bytes.
@defidude (prev kyber/aave/builda) has been shipping this a native desktop/mobile app on testflight, handheld firmware for t-deck / cardputer, rust protocol crates, experimental p2p voice, store-and-forward offline inbox, channels, games, bots.
why this is bigger than chat:
-whatsapp sold for ~$19b as a cloud messenger with phone numbers.
-signal/telegram proved people will pay a privacy premium.
-ratspeak sits under that stack
layered tam i actually care about:
-$6b consumer encrypted messaging (signal/telegram/whatsapp replacement path
-$2.8b off-grid / public-safety mesh. disasters, blackouts, contested networks.
-lorawan already sits on 100m+ deployed devices
-growing agent-to-agent comms. this is the sleeper
other novel use cases people are already talking about:
-builders hosting pages, git, bots, apps on the mesh
-sepolia txs over the mesh with a helios light client. offline-ish ethereum
-@AskVenice inside ratspeak: venice api key powers an agent reachable through e2ee mesh, including from a device that is not on the internet as long as some hop on the path can reach the agent host
agents are about to be economic actors. we need to be able to access them offline as well.
here is how it stacks up against other crypto projects:
-venice base:0xacfe6019ed1a7dc6f7b508c02d1b04ec88cc21bf = private inference product
-dolphin base:0xed664536023d8e4b1640c394777d34abaff1df8f = decentralized inference supply
$RATSPEAK = private transport + identity + offline deliver
pod answers where does the model run. venice answers how do i get private intelligence. ratspeak answers how do two agents (or a human and an agent) talk without a server
the winning crypto breakout into ai case is private inference + encrypted offline mesh communication
a16z 2026 trend list is basically privacy + agents + machine-native payments:
-privacy as crypto moat: reticulum encrypts the outgoing packet
-agents/ai: the mesh is a permissionless inbox for agents
-crypto as internet infrastructure
-machine payments / x402 need a durable channel like ratspeak
crypto next rail is internet infra. agents still assume always on cloud. @ratspeakorg is the encrypted comms layer a human, a handheld, and an agent can share when that assumption breaks
Claude didn’t “endorse” NAIVES by @mannay.
But @claudeai highlighted Mannay’s JavaScript face doodles as a favorite Claude Code project.
That became part of NAIVES’ creative DNA.
More interesting provenance than the NFT narrative itself.
My hot take on ACK's 'Argonauts' drop
There will be a twist. Art will reveal to something else or a burn or some other mechanic.
This is not the final form...
Effective today, we are:
1) Doubling Claude Code’s 5-hour rate limits for Pro, Max, and Team plans;
2) Removing the peak hours limit reduction on Claude Code for Pro and Max plans; and
3) Substantially raising our API rate limits for Opus models.