Self-custody vs custody — why 'the platform can't ban you'
Crypto wallets split into two classes: **custodial wallets** — Binance / Coinbase / OKX's built-in centralized-exchange wallets. The platform holds the private keys; your account functions like a bank account, the displayed balance is a number in the platform's database, withdrawals require platform approval. The platform can: freeze accounts / ban on KYC failure / return funds per court order. **Self-custodial wallets** (non-custodial) — MetaMask / Trust Wallet / TokenPocket / SpeedWallet / Phantom fall here. The 12-word seed phrase (BIP-39 standard) is **generated locally on the user's device**, never uploaded to servers. The platform is just an 'interface' helping you call blockchain nodes. **SpeedWallet is the latter.** Implications: (1) the platform can't ban you even if it wants to (no private key); (2) lose the seed and the platform can't recover it — fully user responsibility; (3) no KYC — signup only needs a password + backing up the seed, no ID / phone / email required; (4) regulatory gap — US SEC / Hong Kong SFC / EU MiCA all have limited enforcement reach over self-custody; they can constrain connected DApps / trading features but not the wallet itself.
Globally available — BLOCKED_REGIONS empty
SpeedWallet has **no country-level blocks** in AF3's matrix, BLOCKED_REGIONS = []. Why: (1) **the app is a pure client-side tool** — like a calculator or offline notebook, keys generated + transactions signed on-device, servers only optional node proxies; even if servers are blocked somewhere, users can still use local seed + their own node to reach the chain; (2) **no fiat on-ramp / off-ramp to sanctioned regions** — built-in crypto purchase (via MoonPay / Ramp / Transak) auto-disables in sanctioned countries (Cuba / Iran), but the wallet itself isn't disabled; (3) **download-channel limits are the only practical barrier** — mainland China App Store removed nearly all crypto wallet apps in 2024 (per mainland financial regulation); users must switch Apple ID region or sideload Android APKs. Store-review issues aren't blocks — technically the app runs in mainland, RPC nodes (infura.io / alchemy.com) are mainland-reachable. AF3 rates SpeedWallet as ✅ OK for global IPs; only download stage may need VPN for Apple ID region switch.
Mobile-first vs MetaMask's desktop ecosystem
SpeedWallet's core differentiation: **mobile-first**. MetaMask originated as a browser extension (Chrome / Firefox) released in 2016, mobile app came later, but desktop is its home — DApp interactions (Uniswap / Aave / OpenSea etc.) happen mostly in desktop browsers. SpeedWallet is the opposite — iOS / Android native app from day one, barely any desktop (web version has limited features). Real differences: (1) **UX** — mobile fingerprint / FaceID unlock, swipe between accounts, gesture QR scans — SpeedWallet's native mobile interactions flow better than MetaMask mobile; (2) **DApp connection** — SpeedWallet relies on WalletConnect v2 for mobile DApp connections (QR scan / deep links), desktop-DApp connection experience trails MetaMask browser extension's direct approach; (3) **hardware wallet support** — MetaMask supports Ledger / Trezor (desktop extension direct), SpeedWallet mobile's hardware support is limited, typically needs WalletConnect indirection; (4) **multi-account management** — mobile app's account-switching flow isn't as smooth as desktop extensions, suits single-account / low-asset users. Recommendation: DeFi power user / desktop-heavy goes MetaMask; mobile-first / multi-chain QR interactions go SpeedWallet or Trust Wallet.
Multi-chain support — major EVMs + Solana + extensible
SpeedWallet's main supported chains (as of early 2026): (1) **EVM mainstream**: Ethereum (mainnet + Sepolia testnet) / BSC (Binance Smart Chain) / Polygon / Avalanche C-Chain / Arbitrum One / Optimism / Base (Coinbase L2) / Fantom; (2) **non-EVM**: Bitcoin (BTC, SegWit / Taproot) / Solana (SOL, popular meme-coin chain) / Tron (TRX, low-fee USDT network); (3) **emerging L1 / L2**: added dynamically based on market heat, e.g., Blast / Linea / zkSync Era typically within a month of launch. User experience: adding a new chain is easier than MetaMask (pre-filled RPC, no manual chainId / RPC URL / explorer link), but custom chains (enterprise internal testnets) are less flexible than MetaMask. Native token per chain + ERC-20 / SPL / BEP-20 tokens all visible, NFT display supports ERC-721 / ERC-1155 / Solana Metaplex. Bridge (cross-chain): built-in cross-chain aggregator (typically LI.FI / Socket), users can bridge in-app without going to bridge.arbitrum.io / bridge.optimism.io. For AF3 VPN users: RPC node access is network-affected; mainland China direct connection to Infura / Alchemy is occasionally unstable, VPN fixes it immediately; Solana's official RPC has slightly worse mainland accessibility than Ethereum RPC.
Privacy + security — self-custody's double-edged sword
SpeedWallet's self-custody model is naturally strong on privacy — no KYC, wallet addresses don't directly bind to personal identity. But it also pushes all responsibility onto the user: (1) **seed leak = funds zero**. The seed (12 or 24 English words) is the only recovery key; captured by a phishing site / malicious extension / phone trojan and it's over. **The wallet vendor will NEVER proactively ask for your seed**; any support message / popup / email asking for the seed is a scam. (2) **Airdrop phishing / malicious DApp approvals**. You may receive unknown NFTs / tokens as airdrop; opening them redirects to a malicious DApp requesting 'Approve' token authorization — after signing, all balances of that token get drained. Fix: don't sign unknown DApp approvals; use revoke.cash to periodically revoke old approvals. (3) **RPC node monitoring privacy** — default RPCs (infura.io / alchemy.com) can see queried addresses, initiated transactions, timestamps — combined with IP, deanonymization is possible. High-privacy users can run their own RPC node (archive node + local Geth) or use Privacy Relay (Taho / MetaMask Blockaid alternatives). (4) **VPN's role in on-chain privacy is limited** — VPN only obfuscates IP, but wallet addresses themselves are public on-chain; without mixer / Tornado Cash-level processing, any observer can see transaction history.
AF3's SpeedWallet node strategy — low strictness + nearest RPC
AF3's SpeedWallet detection is similar to other self-custody wallets (TokenPocket / Trust Wallet), strictness 1★, lenient IP scoring (residential 30 / quality_vpn 30 / normal_vpn 28 / datacenter 27). Probes: (1) main speedwallet.app (or .io); (2) API api.speedwallet.app; (3) download pages (App Store / Google Play deep links); (4) built-in RPC origins (typically Infura / Alchemy / QuickNode aggregations); (5) WalletConnect (wc.app / relay.walletconnect.org). Node-recommendation logic: (1) RPC latency matters most — transaction signing + broadcast needs low-latency RPC, under 100ms ideal, over 200ms can leave transactions in pending longer (not because chain is slow, RPC origin is slow); (2) US / European nodes friendliest to mainstream EVM RPCs (Infura / Alchemy main DCs in US-East); (3) Asian nodes friendly to Solana RPC (Solana official RPC has Singapore / Tokyo mirrors); (4) avoid remote nodes (some African / Latin American ISPs timeout on Infura / Alchemy TLS handshake). Mainland China users practically: direct works but RPC is unstable (DNS poisoning + TLS MITM); VPN stabilizes it almost instantly. AF3's advice: wallet users don't need to be as picky about nodes as video / music users — any stable VPN suffices; **protecting the seed phrase and device security matters more** — network issues and on-chain security are two different axes.