Loops HouseBridle

NEAR HACKATHON
Team
1 member- HAOwner
Hailey
Overview
Bridle gives an AI agent a DAO's money on Base without giving it any key.
The problem: a DAO that wants an agent to manage funds on another chain either hands the agent a key (one prompt injection away from losing everything) or signs every step itself (no agent). A NEAR DAO also cannot own EVM-side policy modules.
Bridle is a NEAR contract with no full-access key. It acts as the policy module for a Sputnik DAO's Chain Signatures account.
How a request flows:
- The agent holds a function-call key that can only call
agent_act, and it can only ask: "supply 30 USDC to Aave". - The vault checks the request against the mandate the DAO voted for (caps, quotas, intervals) and reserves the funds and the Base nonce.
- It builds the EIP-1559 transaction itself and has the NEAR MPC network sign it.
- It counts the step as done only when the same MPC network attests the transaction succeeded on Base, carrying the exact log the vault expects. The vault verifies that attestation in-contract with ecrecover.
Refusals are recorded on-chain. DAO changes that loosen the mandate or move more than a small per-epoch amount out wait in a public queue that guardians can veto. Guardians can pause and unwind positions but cannot move funds out.
It runs on NEAR testnet and Base Sepolia with Aave v3:
- A prompt-injected agent asked to "send ALL funds to 0x…" is refused on-chain.
- An over-limit DAO outflow is parked, then vetoed.
- Supply, withdraw, deposit, cancel, upgrade and unwind all run live, each step with an MPC landing proof.
make demo replays the whole story offline in about 2 minutes. Golden tests reproduce live MPC attestations byte for byte. A wasm check proves the contract cannot add a full-access key or delete its account.
NEAR fit:
- Chain Signatures signs for the vault's derived Base address.
verify_foreign_transactionproves landings.- Function-call keys bound the agent and guardians.
- Sputnik DAO is the owner.