Rabby wallet is a browser extension wallet built by DeBank, designed as a direct upgrade to MetaMask for EVM-chain power users. Where MetaMask shows you a raw hex transaction and asks you to sign it, Rabby simulates every transaction before you confirm it — displaying exact token balance changes, approvals, and risk flags in plain language. This guide covers everything: installation, transaction simulation, multi-chain portfolio, Ledger and Trezor integration, and how to migrate from MetaMask.
What Is Rabby and Who Makes It
Rabby is developed and maintained by DeBank, the analytics company best known for its cross-chain DeFi portfolio tracker at debank.com. DeBank launched Rabby in late 2021, positioning it as the wallet that treats signing safety as a first-class feature rather than an afterthought.
The extension supports every EVM-compatible network — Ethereum mainnet, Arbitrum, Optimism, Base, BNB Chain, Polygon, Avalanche, and dozens more — without requiring manual network configuration. It detects the chain a dApp is requesting and switches automatically.
Rabby is open source. The repository lives at github.com/RabbyHub/Rabby, which means the signing logic, phishing-list handling, and simulation engine are all auditable.
Rabby vs MetaMask: Core Differences
The two wallets share the same EIP-1193 provider interface, so any dApp that works with MetaMask works with Rabby. The differences are in user-facing safety and UX:
- Transaction simulation: Rabby simulates every transaction and shows you net balance changes before you sign. MetaMask added a basic version of this in v11, but Rabby's implementation is more granular and has been there longer.
- Approval management: Rabby surfaces your outstanding ERC-20 and NFT approvals directly in the interface with one-click revocation. MetaMask has no native approval screen.
- Auto-chain switching: Rabby switches networks automatically when a dApp requests it; MetaMask prompts you to confirm every switch.
- Multi-address portfolio: Rabby aggregates balances across every address you add, powered by the same DeBank indexer behind debank.com.
- Phishing detection: Rabby maintains a blocklist of known phishing domains and flags them at the point of connection, before you even reach the signing screen.
MetaMask's main advantages remain ecosystem inertia, a mobile app, and Snaps extensibility. For pure browser-based DeFi work, Rabby is the stronger tool.
How to Install the Rabby Browser Extension
Rabby is available for Chromium-based browsers (Chrome, Brave, Arc, Edge) and Firefox. The Chrome Web Store listing is the safest installation path.
- Open the Chrome Web Store and search for "Rabby Wallet", or navigate directly to the official Rabby extension page. The extension ID is
acmacodkjbdgmoleebolmdjonilkdbch— verify this ID matches before installing. - Click "Add to Chrome" and confirm the permissions prompt. Rabby requests access to read and modify data on all sites you visit — this is standard for wallet extensions that need to inject a provider.
- Pin the Rabby icon to your toolbar via the extensions puzzle-piece menu so it stays accessible.
- Choose your setup path on first launch: create a new wallet, import an existing seed phrase, or connect a hardware wallet.
- Set a local password. This password encrypts your keys in browser storage; it is not your seed phrase and cannot recover your wallet if you lose the seed.
- Back up your seed phrase immediately. Rabby displays it once during setup. Write it on paper, store it offline. Anyone with this phrase controls your funds.
The installed extension weighs roughly 4 MB and does not require a companion app or account registration.
Installing on Brave
Brave's aggressive shield settings occasionally interfere with wallet provider injection. If a dApp cannot detect Rabby on Brave, open brave://settings/shields, find the site, and disable "Block fingerprinting" for that domain. Brave's built-in Brave Wallet can conflict with Rabby's window.ethereum injection — go to brave://settings/web3 and set "Default Ethereum wallet" to "Extensions (Metamask-compatible)" to resolve this.
Transaction Simulation: How It Works and Why It Matters
Transaction simulation is Rabby's flagship safety feature. When you click "Confirm" on any dApp, Rabby intercepts the unsigned transaction data and runs it against a fork of the current chain state before presenting the signing screen.
The simulation output shows:
- Token balance changes: exact amounts of every token leaving or entering your address, denominated in both units and USD value at current price.
- NFT movements: which token IDs move and in which direction.
- Approvals granted: any ERC-20 allowance or ERC-721/1155 approval that the transaction sets, including unlimited approvals flagged in red.
- Contract risk rating: Rabby queries its own risk database and DeBank's contract labeling to show whether the receiving contract is verified, unverified, or flagged.
A legitimate Uniswap v3 swap will show something like: "−0.5 ETH, +1,248.32 USDC" in green and red. A drainer contract will show "Approval granted to [unknown contract] for ALL tokens in wallet" — a red flag that's invisible in MetaMask's default view.
Limitations of Simulation
Simulation is not a guarantee. A few edge cases matter:
- MEV and sandwich attacks happen post-signing, not at signing time, so simulation cannot predict them.
- Upgradeable proxy contracts can change behavior after simulation. Rabby flags proxies but cannot simulate future logic.
- Gas estimation errors mean simulation sometimes fails for complex multi-step transactions. Rabby will show a "simulation failed" warning and let you proceed manually — treat that as elevated caution.
The Rabby security model documentation covers these constraints in detail.
Multi-Chain Portfolio Display
Rabby connects directly to the DeBank indexer, which tracks token balances, DeFi positions, NFTs, and claimable rewards across 100+ EVM chains. This data populates inside the extension without any additional configuration.
Opening the Rabby popup shows your total portfolio value in USD, broken down by chain. Clicking a chain expands token-by-token balances. The "DeFi" tab shows open positions: liquidity pool shares, lending deposits, staking positions, vesting schedules.
Adding Multiple Addresses
Rabby allows you to add multiple addresses under a single extension instance, mixing hot keys, hardware wallet addresses, and watch-only addresses.
- Click the address selector at the top of the Rabby popup.
- Select "Add an address".
- Choose the type: new seed phrase, import seed, import private key, connect hardware wallet, or watch-only (enter any ENS name or 0x address).
- Label each address with a nickname for easy identification.
Watch-only addresses are useful for monitoring cold storage or multisig addresses without importing their keys. The portfolio aggregation works for watch-only addresses the same as signing addresses.
Connecting Ledger and Trezor Hardware Wallets
Rabby has native integration for Ledger (via WebHID), Trezor (via the Trezor Connect bridge), Keystone (via QR code), and several other hardware signers. This section covers Ledger Nano X and Trezor Model T, the two most common devices.
Connecting a Ledger Nano X
- Update the Ledger Nano X firmware to the latest version using Ledger Live. As of 2025-01, firmware 2.2.3 or higher is recommended.
- Install the Ethereum app on the Ledger Nano X via Ledger Live's Manager tab.
- Open the Ethereum app on the device (the screen should read "Application is ready").
- Open Rabby, click the address selector, choose "Add an address", then select "Ledger".
- Click "Connect via USB". Chrome will show a WebHID device picker — select your Ledger Nano X from the list.
- Select which derivation path accounts to import. Rabby shows balances next to each address to help you identify the right one.
- Confirm on the Ledger screen when Rabby requests device access.
When signing transactions, Rabby will display the transaction on-screen and prompt you to verify and confirm on the Ledger Nano X's physical buttons. The private key never leaves the device.
Connecting a Trezor Model T
- Update the Trezor Model T firmware via Trezor Suite. Firmware 2.6.x or higher is required for full EIP-712 typed-data signing.
- Open Rabby, click "Add an address", select "Trezor".
- Allow the Trezor Connect popup to open. If it is blocked, allow popups from
connect.trezor.ioin Chrome settings. - Authorize the connection on the Trezor Model T touchscreen.
- Select the account addresses to import into Rabby.
Trezor Model One users should note that EIP-712 structured data (used by Permit signatures on DeFi protocols) displays as a hash rather than decoded fields on the Model One due to firmware limitations.
Migrating from MetaMask to Rabby
Moving from MetaMask to Rabby requires importing your seed phrase or private key. This is safe to do if you follow the steps carefully and are on a clean, uncompromised machine.
Option A: Import Your MetaMask Seed Phrase
- Open MetaMask and go to Settings → Security & Privacy → Reveal Secret Recovery Phrase. Enter your MetaMask password to reveal it.
- Write down the 12-word (or 24-word) phrase on paper. Do not paste it into any text field other than the wallet import screen.
- Open Rabby and select "Import seed phrase" from the setup screen.
- Type the seed phrase into the Rabby import field word by word.
- Set a Rabby password and complete setup.
- Verify that your addresses and balances appear correctly in Rabby.
- Optionally disable MetaMask after migration. Two active wallet extensions injecting into
window.ethereumsimultaneously can cause dApp conflicts.
The same seed phrase controls the same addresses in both wallets. Importing the seed into Rabby does not remove it from MetaMask, and does not change any on-chain state.
Option B: Import a Specific Private Key
If you only want to move one address without exposing your full seed:
- Export the private key from MetaMask: account menu → "Account details" → "Show private key".
- In Rabby, choose "Add an address" → "Import private key".
- Paste the private key and set a label.
Private key import gives Rabby signing authority over that single address. The MetaMask seed phrase that generated the key remains unaffected.
After Migration: Revoking Stale Approvals
The Rabby approval management screen (shield icon in the bottom navigation) lists every outstanding ERC-20 and NFT approval associated with your address. After migrating, spend 5 minutes reviewing this list and revoking any approvals to unrecognized or deprecated contracts. Each revocation is a small on-chain transaction costing a few cents of gas.
Security Track Record
Rabby has not suffered a supply-chain compromise or user fund loss attributable to the extension itself since its 2021 launch, as of 2025-06. The codebase has received third-party security reviews; DeBank has published findings from audits conducted by Least Authority and other firms on their GitHub repository.
Key security properties to know:
- Keys are stored locally, encrypted with your Rabby password, in Chrome's extension storage. Rabby's servers never receive your private key or seed phrase.
- The extension is open source under the MIT license. You can audit, fork, or self-build it.
- Phishing protection is active by default. Rabby compares every site you connect to against a maintained blocklist and a heuristic domain similarity check (e.g., "uniswαp.org" using Cyrillic characters).
- No telemetry beyond anonymous, aggregated RPC usage for chain infrastructure.
One important note: browser extension wallets are inherently less secure than hardware wallets for large holdings. Rabby is best used as a daily-driver signing interface, with the bulk of assets held on a Ledger or Trezor connected to it.
FAQ
Q: Is Rabby wallet safe to use?
Rabby is considered safe for everyday DeFi use. It is open source, has not been exploited at the extension level since its 2021 launch, and its transaction simulation actively reduces the risk of signing malicious contracts. For amounts above a few thousand USD, connect a Ledger Nano X or Trezor to Rabby so signing requires physical device confirmation.
Q: Can I use Rabby and MetaMask at the same time?
You can have both installed, but only one should be set as the active window.ethereum provider in each browser profile at a time. Running both simultaneously causes dApps to behave unpredictably. The practical solution is to use separate Chrome profiles — one with Rabby active, one with MetaMask active.
Q: Does Rabby work on mobile?
As of 2025-06, Rabby does not have an official standalone mobile app. DeBank's mobile app includes a built-in wallet with similar features on iOS and Android, but the Rabby browser extension itself is desktop-only (Chrome, Brave, Firefox, Edge).
Q: Will importing my MetaMask seed phrase into Rabby expose my funds?
Importing a seed phrase into any wallet on a compromised machine is a security risk. If your device is clean, importing your MetaMask seed phrase into Rabby is safe — Rabby encrypts it locally with your password and does not transmit it. The on-chain addresses and keys are identical regardless of which software holds the seed.
Q: What chains does Rabby support?
Rabby supports all EVM-compatible chains. At launch the list exceeded 100 networks including Ethereum, Arbitrum One, Optimism, Base, BNB Chain, Polygon PoS, Avalanche C-Chain, Fantom, Gnosis Chain, zkSync Era, and Scroll. Chain detection is automatic — Rabby reads the chainId from a dApp's connection request and switches without manual network entry. The full supported chain list is maintained in the Rabby GitHub repository.
