Stories from real users, product updates, and what we are building next.
You commit. You stake money. You upload proof. An AI verifies. Honor it and your stake comes back. Miss it and your stake is redistributed to operators who kept their word. The company does not profit from your failure. The people who actually showed up do.
A month ago Balaji told me to pivot. I disagreed publicly and kept building. Then I looked at the validation we already had from a different product and the math became impossible to ignore. This is what we are doing instead, and why it is the same company, just pointed at a bigger problem.
Three pieces of advice in five minutes. I disagreed with one, agreed with one, was already doing one. Five weeks later we pivoted anyway. This post is the before; the May 21 post is the after.
Last week we shipped a Filecoin mirror so receipts could outlive our database. This week we added 0G Storage alongside it. Two independent networks now hold byte-identical copies of every signed receipt. Here is why the second one matters.
Your assistant has been signing receipts on Solana for months. The signature was real, but the bytes lived on our servers. Now those same bytes are also pinned to a public network anyone can fetch from. Here is what that closes, in plain English.
You already have iMessage open. Now your assistant lives there too. Ask in a text, tap to approve the draft, the email lands in your Gmail. No new app to install. Telegram and WhatsApp coming the same way.
Every action your assistant takes leaves a signed receipt. But how do you know the signature came from us and not someone pretending? We publish our signing identity on a public blockchain, so even if our website goes down, you can still check.
You tap, the email sends, the receipt appears. Behind the scenes there is a chain doing the bookkeeping, but you never have to think about it. Here is what that chain is doing and why it stays out of your way.
The single biggest difference between a helpful agent and a dangerous one is a human in the loop at the right moment. Here is how we designed the approval flow.
Every agent action is SHA-256 hashed and the Merkle root is published to a Solana devnet program every N actions. Here is the exact pipeline.
What we protect against, what we do not, and why we made each trade-off. The honest version.
Lawyers, accountants, therapists. Every one of them has a confidentiality obligation that cloud AI breaks by default. This is our wedge.
Not every blockchain is a good audit layer. Solana happens to fit the three constraints: fast finality, cheap writes, verifiable publicly. Here is the math.
Everyone talks about retention like it's a number. It's not. It's a behavior. 93% retention means 93 out of 100 people came back. Not because of push notifications. Because the thing worked.
Historical post from before the 2026-05-22 pivot. The privacy argument made here informed the current trust-stack design (signed receipts on a public chain, two-network mirroring) but the local-first / Ollama framing has been retired.
We're building on Solana because it collapses payment, publishing, and trust into one layer. A developer in Lagos can publish an agent tonight. A user in Tokyo deploys it tomorrow. 400ms settlement.
I built Velocity Esports alone. Got partnerships with Epic Games and Quest Nutrition not because I had leverage, but because I showed up prepared. Three lessons that carry directly into Operator Uplift.
