Arc Testnet only. Every chain, contract and RPC endpoint here points at a testnet.
What's inside
🔐 MeshPort Wallet
A self-custodial wallet you can open with Google or an email code. The key is
generated on your device, unlocked elsewhere with a passkey or a
password-sealed Recovery QR, and never stored by MeshPort. Create or import
a classic wallet with a recovery phrase if you prefer.
→ How self-custody works
💬 Chat & Pay
Message anyone by their .arc username and send money in the same thread.
Chats are end-to-end encrypted, with every chat key signed by its wallet.
→ How chat encryption works
🌐 Multichain Hub
One balance on Arc, reachable from 20+ chains: bring USDC in, send it out,
track every step. Built on Circle Gateway and CCTP V2.
🧾 Payment links & business accounts
Shareable links (meshport.xyz/paylink/you?amount=10) with rich previews,
QR payments, business bills, bulk payouts, swaps (USDC · EURC · cirBTC) and P2P
trading with on-chain escrow.
Self-custody at a glance
sign in ─► key made on your device ─► passkey (Face ID / fingerprint)
└► Recovery QR (a password only you know)
| MeshPort stores | MeshPort never stores |
|---|
| Wallet address, username, profile | Private keys or seed phrases |
| Passkey id + passkey-encrypted key | Recovery passwords or QR contents |
Build
git clone https://github.com/0xsuneel/meshport.git
cd meshport
npm install
npm run dev # http://localhost:5173
npm run typecheck # TypeScript
npm run lint # ESLint
npm run test # Vitest
npm run build # production build
You'll need a Supabase project and a .env — see
Local development.
Repository map
| Path | What it is |
|---|
src/ | React + Vite PWA — wallet, chat, pay, multichain, business, P2P |
src/lib/ | Wallet, passkey, Recovery QR and chat crypto; payment logic |
src/blockchain/ | Balance readers, RPC providers, chain config |
api/ | Vercel functions — link previews, relayer, profile, push |
supabase/functions/ | Edge Functions — claims, accounting ledger, business pay (merchant-pay), indexer |
supabase/migrations/ | Database schema and row-level security |
contracts/ | Solidity — rewards, P2P escrow, bridge router |
docs/ | Architecture, self-custody, chat encryption, audits |
Names in the app vs. names in the code
The app has two account types, Personal and Business. Some code and
database names are older than the app's wording; they mean the same thing:
| In the app | In code and the database |
|---|
| Business account | merchant (useMerchant, isMerchant, merchant_* tables, merchant-pay) |
| Business verification | merchant_applications |
| Cross-chain Transfer (business) / Multichain Hub (personal) | /multichain, MultichainPage |
| Business Insights | /business?screen=reports, BusinessInsightsPage (desktop) |
| Manage money · money on other chains | BusinessMoney, Unified Balance; payment status in_ledger = waiting on another chain |
| Bill · Request · Shop QR payment | merchant_payment_intents (kind = invoice is a bill; via = shop_qr is a Shop QR payment; otherwise a request) |
The ledger folders and ledger_events table (server/ledger/,
supabase/functions/ledger-interpret/) are the internal accounting record
that Activity is built from. It is never shown in the app.
Tech
React · TypeScript · Vite · Tailwind · viem · Supabase · Vercel · Circle
Gateway & CCTP V2 · WebAuthn passkeys · Argon2id · X25519 / AES-256-GCM
Contributing & security
Contributions are welcome — see CONTRIBUTING.md.
Please report security issues privately rather than in a public issue.
License
MIT
