Loops HouseRevVault

NEAR HACKATHON
Team
1 member- JEOwner
jeremyweb3
Overview
RevVault is revenue-routed credit for AI businesses on NEAR. A business uses a RevVault pay link as its payee. Every customer payment lands in the contract first, and the contract splits it inside the same transaction (ft_on_transfer): part repays the open loan, the rest goes straight to the business. No repay button, no keeper. The credit limit is 40% of the trailing 30-day revenue that actually flowed through the contract (cap 2,000 USDC). A draw costs a flat 3% and is paid directly to a vendor account; the contract rejects the borrower's own account as payee. LPs deposit mock USDC, a first-loss reserve takes the first loss, and each draw mints an inspectable revenue note.
Verify without a wallet: the README has curl commands against the live testnet contracts (revvault.revvault-dep-17094.testnet). biz-agent's limit of 1,280 USDC is exactly 40% of the 3,200 USDC routed; loan ln_001 drew 500, repaid 515 and settled, with explorer transaction hashes in deployments/testnet.json. The web app (Vite + TypeScript) reads the contracts live and guides a business through connect, pay link, get paid, draw, repay (axe-core: 0 violations).
Honest limits: testnet, mock USDC, unaudited. Revenue history is seeded demo data. Repayment is economic, not legal. APY is illustrative. No on-chain vendor allowlist. NEAR Intents has no testnet, so testnet payouts are direct token transfers (a mainnet quote preview is a dry run only). The UI's write paths were built but not exercised end to end. Potentially first-of-its-kind: we found no NEAR-native revenue-routed credit line for agent businesses, which is absence of evidence, not proof.