Loops HouseWrench

NEAR HACKATHON
Links
Team
1 member- SHOwner
Shailendra
Overview
Wrench: audit your wallet privately
On When Shift Happens E193, NEAR co-founder Illia Polosukhin described the trade blockchains made: "We went to a blockchain where everyone sees how much everyone else has... we lost a lot of the privacy." With your balance completely public, he said, "when you pay me, I can check how much money you have."
Run that forward to your own account and it gets specific: the extra full-access key an old app left behind, counterparties you forgot, a balance anyone you've paid can read. Checking it usually means pasting your address into a service you can't inspect and trusting that the report wasn't edited on the way back.
Wrench runs that audit privately and proves it. You sign one NEP-413 message with a fresh nonce, and Wrench checks on NEAR RPC that the key is a FullAccess key of the account, so an account you don't own is refused before any data moves. The account's public data (balance, recent transactions, counterparties, access keys) goes to Qwen/Qwen3.8-27B on NEAR AI Cloud, which runs inside a TEE. Your key and seed stay in your wallet. The enclave signs the request and response hashes and Wrench sends a verify() transaction to the Sworn registry on NEAR testnet; only two hashes and a signature go on chain. The dossier opens after that transaction returns ok:true, with findings ranked by severity.
On the recorded run a demo wallet holding 2.2877 NEAR, with 20 transactions and 3 access keys, came back verified in 22.4 s with one high, one medium and one low finding. A cold click on the hosted page has landed its verify() transaction in 17.1 s, and a receipt with one flipped bit returns ok:false in its own transaction.
NEAR fits because the check itself is a NEAR transaction: the Sworn registry verifies the NEAR AI Cloud enclave's signature on chain, and NEP-413 lets you prove ownership with the wallet you already use.