Loops HouseAuthority Ledger

NEAR HACKATHON
Team
1 member- SAOwner
Sajan Baby P
Overview
Authority Ledger answers the first question in any dispute about an AI agent's action on NEAR: under what authority did it act?
Problem: agents act through access keys. A function-call key limits an agent to one contract and named methods. But once a key is revoked or rotated, a normal RPC node only answers "this key does not exist", so the authority behind a past action is lost.
What it does: paste any testnet or mainnet transaction. Authority Ledger recovers, from public archival records only, the key's permission one block before it signed, whether the call stayed inside it, and the excess authority the key carried (a full-access key signing a call a scoped key could have signed is flagged). It then finds the block where the key was created and removed by binary search over archival state, and names the keys that granted and revoked it, with no indexer. Every finding links to the raw RPC record. It states what records cannot show, such as who held the key.
NEAR's role: access-key permissions, archival state queries, state-change and receipt records. Read-only CLI and web page, verified on real testnet transactions. Built solo during the hackathon.