Loops HouseFireKey

NEAR HACKATHON
Links
Team
1 member- VAOwner
Vampirot
Overview
FireKey lets an AI agent pay on your behalf from a private Zcash balance, within limits you set.
Problem: funding an agent means a hot wallet on a transparent chain, so anyone sees how much you hold and every payment. Agents can be prompt-injected into paying attackers, limits in software on the agent's own machine can be switched off, and agents cannot judge who they pay.
What we built: your ZEC stays in a shielded Zcash vault behind a 2-of-3 FROST key (agent signer, policy cosigner, you). Every spend needs a signed, numbered receipt from a Baochip-1x running our firmware: it holds your per-payment cap and budget, and waits for a press on its button above the cap. Only the approved amount leaves the shielded pool.
How NEAR fits: NEAR Intents 1Click swaps each approved amount into USDC and delivers it to the agent's payment contract on NEAR; both signers verify the 1Click quote signature first. The agent spends only through our firekey-pay contract, with a function-call key that can do nothing else. The contract enforces caps, daily limits and an "ask me above" threshold, verifies device receipts on chain (env::ed25519_verify), and before every payment checks firekey-registry, a shared on-chain scam list, in a cross-contract call. firekey-check rates receivers from NEAR RPC and NearBlocks: allow, warn or block.
On mainnet with real funds: 0.001 ZEC became 0.898 USDC under the cap; 0.002 ZEC became 1.800 USDC after a press on the chip; a prompt-injected payment to a reported scammer was blocked, and the attacker's direct call with the agent's own key was refused on chain. The owner's audit matched every spend to a chip receipt. MIT licensed, with tests, evidence and a threat model in the repo.