MetaMask

MetaMask launched in 2016 as a Consensys side project to get normal browsers talking to Ethereum. Before that, using dApps meant CLI pain or clunky desktop wallets. The extension injected a Web3 provider into the page, popped a confirmation when a site wanted a signature or send, and became the muscle memory of crypto. Mobile followed. Portfolio at portfolio.metamask.io became the wider dashboard for balances, bridges, and staking flows. Tens of millions of monthly users later, most EVM apps still design and test against MetaMask first.

Custody model is classic self-custody. Install from the official site or store. Create a wallet. Get a Secret Recovery Phrase (usually 12 words). That phrase derives every account. MetaMask does not hold it for you. Lose it or paste it into a fake “support” site and the funds are gone. Password / biometrics unlock the app locally. Pair with Ledger or Trezor if you want keys offline and MetaMask as the UI. That combo is still the sensible setup for serious balances.

Day-to-day: add networks (Ethereum mainnet, Arbitrum, Base, Optimism, Polygon, Linea, custom RPCs). Hold ERC-20s and NFTs. Hit Connect on Uniswap, Aave, OpenSea-style markets, or whatever L2 app is shipping this week. Approve token spends carefully. Revoke stale allowances when you can. The wallet also does in-app Swaps (aggregator over DEXs), bridging via partner routes, fiat buy/sell through third parties, and ETH staking shortcuts. Convenience is real. Cost is real too: MetaMask’s own service fee on swaps and many bridge-style routes is commonly 0.875% on top of gas and any provider spread. Power users often connect MetaMask to a DEX or aggregator tab and skip the in-wallet swap for size.

Snaps are the modular layer. Third-party packages add transaction insights, notifications, Bitcoin / Solana-style support, and other network or security tooling without rewriting the whole wallet. Quality varies by Snap author. Install only what you need and treat Snap permissions like dApp approvals. Native multichain pushes (including Solana in the extension story) keep narrowing the old “EVM-only” complaint, but MetaMask’s home turf is still Ethereum + EVM L2s. Phantom still feels more native on Solana. Rabby often feels clearer on EVM simulation and multi-account safety.

Security posture improved a lot since the early years. Blockaid-style transaction simulation / malicious-tx alerts, privacy-preserving security warnings, address-poisoning checks, and smarter approval UX catch a chunk of drainers before you click Confirm. Smart Accounts / account-abstraction work (ERC-4337, EIP-7702 paths, passkeys, seedless onboarding via social / Web3Auth-style rails after Consensys acquisitions) aims at gas abstraction, batching, spending limits, and recovery that is less “tattoo the seed phrase.” Those features are rolling and uneven by platform. Classic seed wallets remain the default mental model for most users.

What MetaMask is not: a bank, customer support that can reverse a send, or a cold vault by itself. Phishing clones of the extension, fake MetaMask sites, Discord “admins,” and signature phishing still drain people daily. Default Infura / Consensys RPC and telemetry settings bother privacy maximalists; swap RPC endpoints if that matters to you. No traditional 2FA on a seed-based EOA. The password only unlocks the local vault.

Versus competitors: Rabby for sharper EVM simulation and fee clarity. Phantom for Solana-first UX (now with EVM). Hardware wallets alone for long-term storage without a browser. Coinbase Wallet / exchange wallets if you want recovery hand-holding and accept custody tradeoffs. MetaMask wins on ubiquity. If a random EVM dApp has one wallet button that always works, it is usually this one.

Who it’s for: anyone living in Ethereum DeFi, NFTs, and L2s who wants self-custody and maximum dApp reach. Who should skip heavy reliance on it: people who only buy and hold on an exchange, fee-sensitive high-frequency swappers, and anyone who will not protect a seed phrase or use a hardware wallet for large stacks.

STRENGTHS

- Default dApp compatibility across Ethereum and EVM L2s. Industry reference wallet

- Self-custody with clear seed / account model and solid hardware wallet pairing

- Extension + mobile + Portfolio covers connect, manage, swap, bridge, stake in one brand

- Snaps and smarter multichain support extend beyond pure EVM without forcing a second wallet for every experiment

- Security alerts, tx simulation, and address-poisoning defenses reduce (not eliminate) common drain paths

- Smart Accounts, passkeys, and seedless onboarding paths modernize UX for newer users

- Huge user base and Consensys backing. Features and docs ship continuously

WEAKNESSES

- Hot wallet by design. Compromised browser, phone, or leaked seed = loss. No Magical Support refund

- 0.875% MetaMask fee on in-wallet swaps / many bridge routes stacks with gas and is expensive at size

- Phishing and malicious approvals remain the main failure mode. Product alerts help; user error still dominates losses

- Classic EOAs lack native 2FA. Seed phrase is a single point of failure if mishandled

- Default RPC / analytics posture is weaker for privacy-focused users unless configured

- Snaps and third-party fiat / bridge partners add attack surface and fee opacity

- UX and network management still confuse beginners (wrong chain, unlimited approvals, lookalike tokens)

- Solana / non-EVM experience is improving but still second to dedicated wallets for power users on those chains