Loops HouseThriveeShield

NEAR HACKATHON
Links
Team
1 member- AFOwner
Affan Ahmed
Overview
ThriveeShield reads a payment request before anything is signed, for AI agents and for people.
For agents: an agent that can pay can be tricked into paying, and one prompt-injected email is enough. ThriveeShield gives the agent a NEAR function-call access key scoped to one vault contract and two methods, never a full-access key. A risk service scores the receiver (account age, contract code changes, payment history, a shared blocklist with evidence) and returns allow, warn or block. The vault contract enforces the same verdicts on-chain: unknown receivers are held until the owner approves, blocklisted or over-limit payments are refused and logged. An agent that skips its own checks still cannot pay a bad address.
For people: a browser extension wraps the signing calls of NEAR wallets and checks each request before the wallet is asked. It blocks requests that add a full-access key, delete the account or install code, and warns on new receivers, large amounts and asset approvals. It is written for Meteor, HOT, Intear, Nightly, Sender, Bitget and OKX, and has not yet been tested against the real wallet extensions.
Try it with no install at https://shield.thrivee.tech: a simulated scam site runs the extension's own checking code, and an account check-up reads any NEAR account's keys and recent transactions from the chain, scores them, and adds an AI summary.
Evidence: 29 contract tests, 63 unit tests, and five attack scenarios on a local NEAR sandbox (24 checks). Testnet was not run. NEAR tools: a Rust smart contract (near-sdk), function-call access keys, near-api-js, near-sandbox, NEAR RPC and NearBlocks. Code written with Claude Code and Google Antigravity; details in the README.