Loops HouseCommons: Telegram group treasury

NEAR HACKATHON
Team
1 member- JOOwner
John Tran
Overview
Problem: A group's shared money (prize money, an event budget, a club fund) sits in one member's wallet. NEAR Hackathon itself pays each prize in a single payment to one account. Everyone else trusts that person, and if their key is lost or stolen, the group's money goes with it.
Product: Commons is a Telegram group treasury. Members tap Join in the chat; the Mini App creates a named NEAR account whose key is generated on their phone and never sent to our server. No wallet app. A founder creates the treasury: an unmodified Sputnik DAO v2 with the founders as council. A council member types "/spend 25 NEAR @huc monitor"; the bot files a Transfer proposal; members see what the contract will do (read from the chain) and sign act_proposal on their own phone. At a majority, Sputnik pays out by itself.
How NEAR fits: Sputnik DAO holds the money and enforces the vote. The bot's DAO role can only add proposals: on testnet the contract refused the bot's vote and its attempt to change the rules (ERR_PERMISSION_DENIED, tx links in the README). npm run verify -- checks this on any DAO, and that the DAO runs the factory's unmodified Sputnik code. Named sub-accounts tie every vote and payment to a person. NEAR Intents 1Click shows live prices for chipping in USDC or USDT from Base, Arbitrum, Solana, Ethereum or Tron.
Limits: testnet only; no real group has used it yet; the cross-chain deposit step is not built (prices only); every vote and payment is public; a lost phone means the council replaces that member through a Sputnik UI.
Check it without keys: npm ci && npm test && npm run demo && npm run verify.
Bot: @commons_near_bot