
Best pitch i've done so far for @arete_a4 Solana Summit Serbia @SuperteamBLKN
✓Building financial sandboxes for agents @arete_a4. Decade in tech. Elec eng. Agent whisperer

Best pitch i've done so far for @arete_a4 Solana Summit Serbia @SuperteamBLKN

If agents are going to handle most onchain volume in the future we need a safer way to do it Coming soon arete.run


Sat down with @0xLinnyx0 to chat about how @arete_a4 lets your agents use @solana safely. Shout out @superteam @SuperteamBLKN for the opportunity

One of the things I want to solve while at SF is sprawl. There’s *so* much you can do on Solana. So many protocols. The implementations, even to use protocols that do the exact same thing, vary widely and involve heaps of SDKs. Plus there’s no discoverability. Soon™ I hope

Everyone complaining about running out of Grok bot limits while i've got Grok dishing out orders to spend my Claude sub tokens

Agents shine a light bright enough to expose how insecure absolutely everything is. They are a forcing function that will make all software secure for the first time. This was my argument in favour of immutable contracts on evm. If everyone can see your code and its immutable only the strongest survive. But their strength and trust will be far beyond anything we have ever seen. Same applies for everything now

High chance we start to view human written code as immoral in security critical situations. Believing you can write more secure software than a swarm of frontier agents is just hubris. Even if you don't think we are there yet (we are) just look at the trajectories

Arete registry is like npm for Solana programs. Install typed SDKs to read accounts and build transactions. Your agent also gets the knowledge to choose programs and see how they fit together. Add live data when you need it. Compose them into a protocol when the product has a real lifecycle. arete.run?utm_source=x&utm_m…

Agents like types. Guards, authority, and state machines give them a feedback loop that “just call the program” doesn’t. arete.run?utm_source=x&utm_m…

An app isn’t a single transaction. It’s a whole flow eg: open → closed → succeeded or failed → claim or refund. Who can contribute. Who can finalize. What happens after the deadline. That’s a protocol. Arete lets you write it once, test it on a mainnet fork, then ship the same client to your app and your agent. arete.run?utm_source=x&utm_m…

I used @aretea4 to build an app that automatically moves your USDC into the best lending pool on Solana. No rates API. No new on-chain program. Arete never holds your keys. Here's how I did it: The app is called Savings. It shows live USDC rates from Kamino, Save and Jupiter Lend. They're Arete live views, so they stay current as the chain changes. I built and tested it on an Arete dev environment, my own private fork of mainnet. The protocol Arete has a registry of existing Solana programs. I installed the three lending programs with one a4 install. Then I described the steps: open an account, deposit, withdraw. Each step says who signs it, what has to be true first, and which instruction to call. Arete turns that into transactions and a typed client for the app. Auto-save You pick how big a rate gap is worth a move, then approve the limits: • the most per deposit • a cap on fees • only these markets • 90 days You sign that once. The automation can only act inside it, and you can pause it any time. The automation A small backend watches the live rates from Arete views. When another market beats yours by enough, it returns a step. Arete checks that step against your consent and simulates it, then Privy signs it. It works with more than just Privy Privy makes it hands-off, but nothing depends on it. With Phantom or Solflare, the user signs each step themselves. Same steps, same guardrails. And when you want your money back, you withdraw. No lockups. That's Arete: protocols from programs that already exist, live on-chain data, and automations that only act within limits you sign. Docs: docs.arete.run

Can't believe I live in a timeline where someone could get drained because of an RCE in their wifi enabled washing machine



Agents like types