Loops HouseNearBy

NEAR HACKATHON
Team
1 member- DAOwner
Dastanbek Samatov
Overview
NearBy lets one phone pay another when neither has internet, and settles the payment on NEAR once any phone carrying it finds a signal.
Problem: digital money stops when the network does. Internet shutdowns, power cuts and payment outages push people back to cash.
Product: a Flutter app, a Rust relayer and a NEAR bond contract. A payment is a voucher: a NEAR Intents USDC transfer (NEP-413) signed on the payer's phone with no network. The receiver takes it by QR or over Bluetooth/Wi-Fi and checks it offline against a balance attestation signed by the relayer. Nearby phones pass vouchers phone to phone (up to 8 hops) until one with a signal uploads them; the relayer can only submit a voucher, not change it, and a signed receipt travels back. Offline risk is bounded: 25 USDC per payment, and every payer locks a NEAR bond that is slashed, and the key banned, when two vouchers with the same sequence number prove a double spend. Users top up with NEAR from any wallet or exchange, swapped to USDC by NEAR Intents 1Click.
How NEAR fits: vouchers are plain NEAR Intents transfers settled by execute_intents on intents.near, so there is no custom token and no custody; implicit accounts make a phone's key its account; the bond contract runs on NEAR.
Shown on mainnet with two iPhones: QR payments in airplane mode, a voucher carried out by a second phone over the radio link, a slash, and an in-app top-up. Limits: small amounts, a demo relayer on a laptop, and a bond contract owned by the relayer account.