// the find
tahowallet/extension
Taho, the community owned and operated Web3 wallet.
Taho is a browser extension Web3 wallet positioning itself as the community-owned alternative to MetaMask. It's a full-featured Ethereum wallet with multi-chain support, NFT tracking, DApp connections, and hardware wallet (Ledger) support. The target audience is developers and users who distrust the MetaMask/Infura/ConsenSys stack on ideological or censorship-resistance grounds.
The background/UI package split with an explicit trust boundary is a genuinely good security decision — `ui` is treated as untrusted code and key material lives only in `background`, reducing the blast radius of a UI-layer XSS. The validator generation pipeline (pre-compiling JSON schemas to avoid `unsafe-eval` in the CSP) is the right call and shows the team thought about extension security seriously. There are 36 numbered Redux state migrations with individual files, which is the correct approach for a wallet that can't break users' existing encrypted storage. The test suite has real integration tests hitting chain services and IndexedDB, not just unit tests with mocks.
The project has been slow — last meaningful activity suggests it's not actively maintained at the pace the wallet space requires; MetaMask has continued shipping while Taho stalled. The build is environment-dependent enough that Firefox submissions require a Docker container to reproduce deterministic output, which is a red flag for an open-source wallet claiming reproducibility. The community-ownership and governance token story (`DOGGO`, earn utilities, Island service) adds significant complexity to what is already a complex codebase, and most of those features appear to be dead or vestigial given the project's current state. Onboarding a contributor requires yarn, nvm, pre-commit, jq, and optionally a local Hardhat fork — the toolchain friction is high and the macOS-only setup script signals that Windows and Linux contributors are second-class.