Walrus

We’ve always said there’d be disputes once agents started acting for people, especially in commerce Any time someone acts on your behalf, there’s a gap between what you asked for and what they did With people, we close that gap with things like contracts, receipts and signatures. But agents are different They’ll make thousands of decisions for you, far more than anyone could check. And none of those decisions comes with anything that proves what you actually agreed to So disputes are coming either way, and we need a way to settle them As far as I can see, there are 3 ways this can go The first is sharing your login with the agent, which is what a lot of people are doing today The problem is that the agent then looks exactly like you. Nobody can separate what you asked for from what it decided on its own The second is letting every platform keep its own logs and trusting them. That falls apart the moment two sides disagree, because each one is holding its own version The third is giving agents their own authority with clear limits, plus a shared record of what they did with it That third option sounds simple, but it puts real demands on the infrastructure underneath 1. The proof has to sit somewhere neither side controls 2. Once it’s written, nobody can change it without everyone seeing 3. Anyone in the dispute has to be able to verify it on their own 4. It has to hold up at agent scale, which means a huge amount of data kept available for a long time A regular cloud account can’t give you that on its own. Cloud storage is fine for the private details. But the proof can’t depend on trusting one company, because trust in one party is the first thing to go in a dispute The proof needs a different kind of infrastructure, and @WalrusProtocol is a good example of what that looks like It’s run by many independent operators, so no side in a dispute controls it Each piece of data stored on Walrus is tied to an ID made from its own content. That means no one can change the proof once it’s stored. A record either matches its proof or it doesn’t, and there’s no way to fake the match Access can be limited to the parties involved, so nobody outside the dispute can read it. Each of them can check the proof on their own, without going through the other side It’s also built to keep a huge amount of data available for the long run. Even if some operators go offline, the data will still be there That’s one of the reasons Walrus is core infrastructure for VAA