Loops HouseSettle Keys

NEAR HACKATHON
Links
Team
1 member- AMOwner
Amit Kumar
Overview
The problem: a company that holds stablecoins has two bad choices today. One shared wallet, where anyone with the key can drain it, or a multisig, where every payment waits for signatures, which is why nobody uses one for the hundred small payments a week. Cards solved this in the fiat world: each person gets a limit, and the limit is revocable.
What we built: Settle Keys, a business account on NEAR where every person gets a key with a limit. A company holds USDC in its own NEAR account. The founder issues each member a key with a policy: which suppliers it may pay, how much per payment, how much per day, and when it expires. A tool gets the same kind of key as a person. Removing someone is deleting their key. The company account holds NEAR for gas; members never do. A Rust contract with 27 unit tests, TypeScript scripts for every step, a three-page app (Team, Pay, Supplier), and a hosted demo. Try it with no account and no faucet: pnpm install && pnpm near:demo. Your own company takes a few minutes with pnpm near:setup.
How NEAR fits in: a NEAR access key can be locked to one contract and named methods. A member's key can call one method, pay, on the company account, and the protocol refuses anything else before any code runs. The contract, deployed on that account, finds the policy by the key that signed, checks supplier, limits, expiry and memo, reserves the amount, and moves the USDC in the same transaction. Refusals come back in the contract's own words. The contract adds and deletes member keys itself, as linkdrop does, so the founder's daily key is a limited owner key that cannot pay. No relayer, no custodian. NEAR Business and Trezu approve each payment with signers or votes; Settle Keys approves once, when the key is issued.