
So today, we're submitting @scrimfinance, built at NEAR HACKATHON (@NEARProtocol) We built Scrim because money on a blockchain is public by default. Anyone can see what you hold and who you pay. And now that AI agents are starting to pay for us, handing them money feels even riskier. Scrim is a private money app for people, teams and AI agents Here is how NEAR makes it work: @near_intents is the core... -> Your private balance lives on NEAR Intents, so the public chain never shows what you hold or who you pay. The same rails let you add money from more than 30 chains, swap, and pay anyone, all without bridges or gas coins on each chain -> For agents, we gave each one its own key and limits: how much per payment, per day, who it may pay, and an end date. Agents connect over MCP, so Claude Code, Codex, Cursor or Gemini can ask to pay, and every request is checked before a person approves it. -> With @out_layer from team @zacodil, an agent can also get its own wallet, with its key held in secure hardware, and pay by itself inside its limits. -> NEAR AI Cloud from @near_ai runs our Ask feature, so you can ask questions about your own money and the answer is computed inside secure hardware and signed. We also used NEAR AI Cloud to attack our own agent. A model with no refusals wrote fake invoices and urgent orders, and talked the agent into trying to pay six times, up to $4,900. The limits stopped every one. You can sign in with a NEAR wallet, Google or email, and it's live today. Try it: scrim.exchange Code: github.com/Datwebguy/scrim If you let an AI agent pay for you, what limit would you set first? Thanks to @ilblackdragon, @avichal, @kain, @hosseeb for this opportunity , and everyone at @NearBuilders @NEARLegion @NEARDevHub #NEARHackathon



















