Loops HouseHyperNear

NEAR HACKATHON
Team
1 member- MAOwner
Max
Overview
Problem: a Hyperliquid master key is a bare address. Whoever holds it can approve any agent, send funds anywhere and withdraw everything. There is no withdrawal lock, no spending cap and no freeze, so a bot, desk or AI agent that trades the account must be trusted with all the money. A hedge also needs two accounts and two orders that nothing on Hyperliquid opens as one action. What it does: an owner logs in with an email or any EVM wallet (Privy) and gets several Hyperliquid accounts (legs) whose keys are held by NEAR Chain Signatures. A public NEAR contract decides what those keys may sign: funds move only between the owner's legs or back to the owner, the AI agent gets a daily cap and a cooldown, and one signed freeze replaces every trading key with a burn address in the same NEAR transaction. The web app has a trade terminal, a hedge opened with one signed command (long and short sent together), TP/SL, grid and TWAP bots on their own legs, an Easy chatbot (Claude fills a fixed form, code checks the order), and agent suggestions (Jev, then Claude) that run only if the owner signs. NEAR features: Chain Signatures (MPC) signs every Hyperliquid owner action; a Rust policy contract; owner intents are EIP-712 signatures checked on chain with ecrecover; any relayer can submit them because the signature is the auth; the agent's function-call key can call only two methods; an optional TEE mode verifies an Intel TDX quote in the contract (testnet, dev registration, not real TDX hardware). Built in the window: the contract, NEAR client, agent, web app, tests and testnet runs. Baseline: a stripped copy of our own Hyperliquid client, tag pre-hackathon, disclosed in the README. Try it (testnet): live app https://hypernear.t09.fun, or with no keys: clone the repo, pnpm install, pnpm test, pnpm build, node agent/src/server.ts --dry-run --serve and pnpm --filter @hypernear/web dev, open localhost:5173, click Explore recorded data. Claims: docs/claims.md.