We ran Rabby as our primary EVM wallet for three weeks, deliberately including risky interactions — unverified contracts, unlimited approvals and a known phishing page from a public blocklist — to test its warnings.
The simulation layer is the product. Before signing, Rabby states the expected change to each token balance and identifies the counterparty contract. In our phishing test the wallet flagged the approval as unlimited and the contract as unverified, in language a non-specialist could act on.
Automatic network switching sounds minor and is not. Rabby detects the chain an application expects and switches, eliminating the class of mistakes where a user sends assets on the wrong network.
The approval manager makes it easy to find and revoke standing allowances, which is the maintenance task most users never perform.
Compatibility is the trade-off. A small number of applications still gate connection to the incumbent wallet, and the mobile app lags the extension in polish.
For anyone signing transactions regularly, Rabby is now our recommendation: 4.6 out of 5, held back only by edge-case compatibility.
Disclosure: tested on a free open-source release with newsroom funds. No compensation was received.
