A new way
to send.

Yes, for supported signing and Bluetooth handoff after the required preparation. Nearby volunteers can store and forward signed packets while your phone stays offline. A relay must eventually connect to the blockchain for submission and confirmation; the sender does not have to be that relay. Forwarding is opt-in and runs while the app is unlocked and open. A delivery acknowledgment is not payment confirmation.

Arc USDC: Create an authorization offline, or prepare the exact payment’s network fee online and approve the saved quote within 60 seconds for sender-paid forwarding. Authorization-only payments need someone to explicitly approve a relay fee; authorizations expire after one hour by default.

SOL: Prepare the exact recipient and amount online. Standard preparation lasts 45 seconds. Advanced users with an existing compatible durable nonce account get a 24-hour app forwarding window; that window does not cancel the on-chain signature.

NEAR: Prepare the exact recipient and amount online. Offline signing has a five-minute app window, also bounded by chain validity.

Shielded ZEC: Sync the wallet first. A saved wallet snapshot no more than one hour old supports local signing. Enter the recipient’s shielded address; a Bluetooth name does not verify it. The recipient syncs its wallet to confirm receipt.

These windows are not guarantees of settlement or cancellation. Resolve uncertain transactions before sending a replacement.

No. Create a new wallet in the app, or restore a compatible wallet using 12 or 24 recovery words. Store your recovery words somewhere private. Never share them with anyone.

This APK supports USDC on Arc, native SOL on Solana, native NEAR and shielded ZEC on Zcash. It requires an ARM64 Android device running Android 8.0 (API 26) or newer. Check the selected network and receiving address before every transfer. Swaps and an iPhone download are not available.

The forwarding implementation passed TypeScript checks and 184 automated tests, including real signatures and durable storage with simulated Bluetooth and network responses. Earlier funded Arc and shielded Zcash testnet transfers were confirmed. A funded NEAR testnet transfer also passed offline signing with network access blocked, finalized receipt and a recipient balance check. The new Zcash native path signed with the emulator disconnected, recovered the saved payment after a cold boot, relayed the same transaction online, and verified receipt in a separate wallet with nine confirmations. Bluetooth radio forwarding was simulated, not tested on physical phones. Funded SOL transfers, physical Bluetooth compatibility and an external independent security audit have not been completed in this release work.

Change your profile picture and display name in Profile → Edit. Choose a photo with Android’s system picker or switch back to initials. Photos stay on your device; imported images are resized and re-encoded to remove image metadata. Your wallet may ask you to unlock again after using the picker.

Updated USDC, SOL, NEAR and ZEC icons. Asset rows show token quantities and estimated USD values using public market prices. Missing or expired prices display a dash.

Added persistent Bluetooth forwarding, prepared offline signing and recipient payment history. Relays submit existing signed transactions without automatically spending their own funds. Both devices should update. An uncertain payment stays pending: do not create a replacement until its outcome is resolved.

Wallet keys use device-encrypted storage; signing uses app memory. Bluetooth transport is not confidential. Nearby relays can associate a forwarded transaction with the sending device. RPC providers receive network requests. USD estimates use public Coinbase prices; requests include asset symbols, never your wallet address or balances. The price provider sees your IP address. Quotes expire after five minutes. Arc, Solana and NEAR transactions are public. Zcash uses shielded transactions, but its direct TLS connection exposes your IP address and connection timing to the server; the app asks for consent before enabling this connection. This site counts visits and APK download requests. A random tab identifier, stored in session storage, prevents repeat counts for 30 minutes; the counter service retains it for that period alongside aggregate totals. Counters do not store wallet details, names or IP addresses. Downloads measure requests, not completed installs. The host may retain access logs. No website account is required. No public support inbox is configured. In the app, use Settings → Report a problem to review diagnostics before sharing.