Loops HouseLeash

NEAR HACKATHON
Team
1 member- QHOwner
Qhodlr
Overview
Leash is an agent wallet that cryptographically cannot overspend.
The problem: give an AI agent a wallet and you have given it the private key. Every safeguard after that (a prompt limit, an orchestration policy, a human check) is something the agent is asked to honour. The limit is a convention.
What it does: Leash is a NEAR contract that exclusively owns a Solana address and signs only transfers that pass its policy. The agent calls the contract, the contract calls the MPC signer, and the agent never holds the key. The agent supplies parameters (recipient, lamports, recent blockhash), never signable bytes; the contract builds the Solana transfer itself. A policy bounds per-transaction amount, rolling 24-hour total, an allow-list (empty means nobody) and session expiry.
How it uses NEAR: Chain Signatures derive the foreign key from (predecessor account id, path) and nothing else, verified in the near/mpc source. When the contract calls sign(), the contract is the predecessor, so the derived Solana address belongs to the contract's account and no other account can request signatures for it. Leash's address derives from (leash-b0c503d6.testnet, solana-1, domain 1). The guarantee needs a locked account (zero full-access keys); both testnet accounts now carry 0 keys.
Deployed on NEAR testnet: contract leash-b0c503d6.testnet, 458,248 B, code hash 59HB5memEzCQMXoWe6mD7KX3ysvYMZoVBHPXVyt4tr64. A live Ed25519 signature from the MPC committee (threshold 11) was verified and a transfer landed on Solana devnet, finalized in 2 s, payee +1,000,000 lamports exactly. 72 unit tests, mutation-checked.
Next: the mainnet deployment is being stood up now. Trust moves to the MPC committee; it does not vanish