Core capabilities
- Key management: generate, import, and protect private keys locally within the extension.
- Transaction signing: approve transactions with an in-extension UI and optional hardware wallet confirmation.
- dApp connectivity: use the extension as a web3 provider to sign messages and transactions for supported dApps.
- Portfolio & token management: view balances, add custom tokens, and monitor activity without exposing keys to websites.
Security model & best practices
Browser extensions increase convenience but also expand the attack surface. Follow these guidelines to minimize risk:
- Install only from the official browser store and verify the publisher name.
- Use hardware wallets (e.g., Ledger or Trezor) with the extension for high-value transactions — require device confirmation.
- Enable biometric or strong-passphrase locks and set a secure extension password where supported.
- Limit permissions: when a website requests wallet access, review the origin and requested permissions before approving.
- Keep the extension and browser up to date; monitor for suspicious activity and remove unused extensions.
Typical workflows
- Install extension → create or import wallet → secure seed and backup.
- Connect to a dApp via the website’s connect button; approve only necessary permissions.
- For trading, confirm order parameters carefully and use test transactions for new contracts or tokens.
- Use hardware wallet pop-up prompts for large transfers to enforce out-of-band confirmation.
Privacy considerations
Extensions communicate with websites and may leak metadata about your activity. To protect privacy:
- Use separate browser profiles for wallet use and general browsing.
- Limit exposure: avoid signing messages or transactions from unfamiliar sites.
- Consider using a VPN or privacy-focused browser when interacting with sensitive dApps.