Electrum is a mature, production-grade Bitcoin wallet with full Lightning Network support, used by thousands of users daily. It is a desktop/mobile application with a daemon architecture, offering three GUI frontends: a full-featured PyQt6 desktop interface, a Qt Quick (QML) mobile interface, and a curses terminal interface. The daemon manages wallet lifecycle, network connections, and exposes a JSON-RPC API. The codebase is highly modular, with a plugin system for hardware wallets (Trezor, Ledger, Coldcard, KeepKey, Jade, BitBox02, Safe-T, Digital Bitbox), label sync, two-factor authentication, submarine swaps, watchtowers, and more. Core features include SPV (Simple Payment Verification) with merkle proof validation, coin selection with privacy-aware heuristics (CoinChooserPrivacy), BIP32 key derivation, mnemonic seeds (BIP39, SLIP39, legacy), and a full Lightning Network implementation with pathfinding (LNPathFinder using Dijkstra with liquidity hints), channel management, HTLC accounting, trampoline routing, and onion messages. The repository also includes deterministic build scripts for Linux (AppImage), Windows (Wine+PyInstaller), macOS, and Android (python-for-android), with reproducible builds using pinned dependencies and hash verification.
This repository is the Tonhub Wallet, a non‑custodial mobile cryptocurrency wallet for the TON blockchain with additional Solana support. It is a full‑featured wallet that supports multi‑account management, token transfers (jettons), staking (liquid staking, native pools), hardware wallet integration (Ledger), a dApp browser using TonConnect v2, and financial products such as the Holders card program and Changelly exchange. The application also includes an AI chat assistant for transaction markup and operations, push notifications via Firebase, and deep‑link navigation for seamless URL handling. Built using React Native and Expo, the codebase is structured around a fragment‑based screen architecture, with custom hooks and React Query for data fetching, Recoil for state management, and a centralized query key factory. Despite its breadth, the codebase exhibits well‑defined separation of concerns with reusable UI components (e.g., ItemButton, RoundButton, WImage) and data patterns (e.g., batched metadata fetching, structural sharing for transaction lists). However, there are signs of technical drift, such as hardcoded endpoints, some deprecated library usage, and platform‑specific native modules that require ongoing maintenance.