Loops HouseNearJar

NEAR HACKATHON
Links
Team
1 member- DAOwner
Danya
Overview
Problem: a near.com account has an internal address that only works between near.com users; near.com warns that funds sent to it from any blockchain are lost. So a near.com user can't simply take money from a supporter holding USDT on Tron, SOL or BTC, and a Sputnik DAO treasury has no link that takes donations from other chains either.
Product: NearJar is a donation jar for a near.com account, payable from any chain. The creator connects the EVM, Solana, TON or NEAR wallet they use for near.com, fills in the jar and signs one message: no gas, no new account. They share one link. Supporters pay from 26 networks (EVM, Solana, TON, Tron, Bitcoin, NEAR, Zcash, XRP, Sui and more): with a connected wallet (EVM, Solana, TON, Tron, NEAR, Bitcoin) or to a one-time deposit address from any wallet or exchange. The donation is swapped and lands in the creator's near.com balance in the asset they picked (USDC by default), in about a minute in the demo. A DAO jar pays a Sputnik DAO treasury instead: the payout is fixed on chain at creation, the page shows the DAO's spending rule, and the DAO endorses or closes its jar by its own proposal.
How NEAR fits: NEAR Intents (1Click) quotes and settles every donation into the recipient's NEAR Intents balance (CONFIDENTIAL_INTENTS: the creator's Confidential near.com balance; INTENTS: a DAO's public intents.near balance). The contract nearjar.near verifies the creator's signature with defuse-core, the code intents.near itself uses, and checks the key with intents.near.has_public_key, so jar ownership follows near.com's own rules. It stores jars, DAO payouts and endorsements, short links and delivered-donation receipts. A relayer with a function-call key makes jar creation gasless; before relaying a DAO jar it checks the DAO's get_policy for the creator's role.
Live on NEAR mainnet: https://nearjar.xyz. The author also submits NearAnyStake, a separate project reusing some of NearJar's wallet and pay code; both READMEs name each other.