Loops HouseAOSI Agent Wallet

NEAR HACKATHON
Links
Team
1 member- CHOwner
Chibuzor-orie Joshua Chukwuebuka
Overview
THE PROBLEM
AI agents can hold a wallet now. Nobody has a good answer to what stops one draining it.
Most teams answer with their own code. A prompt the model can be argued out of, or a check inside the same program the model controls. If that check has a bug, or the model is talked around it, the money is gone.
WHAT WE BUILT
Three layers that fail independently.
A policy gate. It returns a reason instead of a sentence. Over budget. No evidence. Wrong recipient. Purpose too vague. Amount not positive. Every decision is written down before anything moves.
A key with narrow permissions. It can spend up to a set amount, to one address only, calling one method.
A receipt log that can only be added to. Each entry carries a fingerprint of the entry before it, so an old entry cannot be edited without the change showing.
HOW NEAR FITS IN
This is the part that only works on NEAR.
The key is a NEAR function call access key. The NEAR protocol stores its allowance, its allowed methods and its allowed receiver, and the NEAR chain subtracts from the allowance on every call. When the policy gate says no, no transaction is sent. When our code is wrong and tries anyway, the chain still refuses, because the key cannot authorise it.
That is the difference between a limit our software promises and a limit the network enforces.
STATUS
Implemented and runs. 21 tests pass (repo, read 14 Nov 2026). Live on NEAR testnet, account zyphonos-aosi.testnet, key limited to 500 NEAR, one method, one receiver (checked on chain, 14 Nov 2026). Zero customers and zero revenue.
Code and demo: github.com/aosihq/near-agent-wallet