Loops HouseSelkie

NEAR HACKATHON
Links
Team
1 member- MAOwner
Martin Machiebe
Overview
To pay someone in crypto you need their address, and most people don't have one. Selkie lets you pay an X handle instead, from the web app or from a tweet.
If @amaka has never used NEAR, the USDC waits in our escrow contract under a hash of their X user ID (or their handle when the ID can't be looked up). When they sign in with X, Privy creates an embedded NEAR wallet in their browser, Selkie creates amaka.x.selkiepay.testnet with that public key as its only key, and an oracle releases the waiting money into it. Selkie never sees a private key: the explorer and npm run prove:keys show it.
Nobody pays gas. The browser signs a NEP-366 delegate action, and Selkie's relayer submits it only if it matches, byte for byte, what the server prepared for that user.
Tweet to pay: "@SelkiePay send 2 to @amaka" pays on the spot from an X pocket, a small capped balance in our pocket contract. The bot's key can only call pocket_send, only up to your daily limit, only to Selkie accounts. Otherwise the bot replies with a link you sign, then replies again in the thread once it lands, tagging the person paid. "@SelkiePay request 5 from @amaka" makes the ask straight away.
NEAR does the heavy lifting: named accounts make a handle an address; per-account keys make "Selkie holds no key" checkable; meta-transactions make it gasless; ft_transfer_call lets the escrow and the pocket take money and record what it is for in one step. NEAR Intents (1Click) adds money from 10 chains and cashes out to them, or to a bank in Nigeria, Kenya, Uganda or Tanzania through Paycrest: on testnet these show live price previews, and sending is switched on for mainnet.
Also built: pay up to 20 people with one signature, DAO payouts by handle through a Sputnik proposal, push and email notices.
Everything runs on NEAR testnet. Selkie existed on Stellar before the hackathon; all NEAR work is new, and the README links the diff.