Loops HouseIntatto

NEAR HACKATHON
Links
Team
1 member- EDOwner
Eddy
Overview
Intatto is a NEAR vault that gives an AI agent its own trading account. The agent trades through Rhea and NEAR Intents within limits the contract enforces, and can never withdraw. Live on mainnet.
Its Essence: Trading bots hold their users' keys. In 2024 a bug in Banana Gun let attackers drain about $3M, and every transfer was validly signed. Intatto takes the key away from the bot.
What sets it apart:
- The agent never holds a key that can sign a trade outside the policy. On the NEAR Intents path the vault writes the intent itself and the NEAR MPC network signs it for the vault's own account, only for allowed pairs and never below the owner's price floor.
- Its security is a bounty, not a claim. The canary agent's key is public with real NEAR behind it. I attacked it 13 times with that key: nothing moved. The board shows every attempt and the contract's reason for refusing it, and checks the running code against its reproducible build every 10 seconds.
- The AI's decision is tied to the trade. A model on NEAR AI Cloud decided a mainnet intents swap, and the hashes of its answer and its signed receipt are in the swap's own transaction.
The policy: For this, intatto has per-trade and 24-hour caps, receiver, pool and pair allowlists, slippage checked against the exchange's own quote, price floors, a one-call freeze and a withdrawal lock. On mainnet the vault refused over-cap, wrong-pool and loose-slippage trades, a frozen-vault trade, and a prompt-injected agent told to drain it.
Also, an MCP server so any AI assistant can trade through a vault, with a pre-trade check that blocks bad swaps before signing; a 10 bps fee fixed in the code, paid on mainnet; 155 contract, 206 web and 54 agent tests.
The code is unaudited, therefore, the upgrade keys stay until an external audit, disclosed in the README and shown live on the board.
Website: https://intatto.pages.dev