Loops HouseNEAR Agent-Safe Keys

NEAR HACKATHON
Links
Team
1 member- SAOwner
Samuel Aleonomoh
Overview
Problem: if AI agents are going to hold money, the hard part is giving one access to an account without handing it the funds. NEAR has this built in: a function-call access key can call one contract within a gas allowance and cannot move funds. Elsewhere it usually needs a smart-contract wallet with session keys. Is anyone actually using it?
What we built: an investment thesis on NEAR's agent-safe keys in which every number re-runs from one public repo, with no account. We counted every key added on NEAR mainnet from March to October 2026 (BigQuery public dataset) and sampled 300 random blocks (1,521 transactions), checking each signing key on chain.
Findings: function-call keys are under 5% of new keys but sign 13.1% of transactions (95% interval 11.2–15.6%), and intents.near signs two-thirds of those. Additions rose 9x from August to October while transactions rose 7%. A prediction committed before we queried November (at least 2% of new keys) came in at 4.44%. Against: 96–97% of new keys are still full-access, only 1.8% of function-call keys point at agent infrastructure, and fees burnt offset about 1% of issuance, so agent use doesn't move supply yet. Verdict, computed by code from rules written in advance: strengthening, not confirmed.
Second test: PREREG-2.md fixed three predictions for 14 Nov, 06:00–18:00 UTC, and its hash was anchored in Bitcoin block 975,705 before the window opened. node thesis/score-prereg2.mjs scores it by that file's own rules after the window closes, and the repo reports the result, whatever it is.
How NEAR fits: the thesis is about a NEAR-native account feature, and the data is NEAR's BigQuery dataset and public RPC. node thesis/verify.mjs confirms 120 receipts and 20 signing keys on mainnet; the dashboard's Verify button does the same from your browser.