Rabby

Rabby is an open-source browser wallet for Ethereum and EVM networks. Its distinctive security role is inside the signing workflow: it turns a dapp request into a review of likely balance changes and potential risk before the user authorises an onchain action.

A dapp request is not the same as a wallet approval

A connected application sends interaction requests through the browser Ethereum-provider interface, and Rabby routes them through its wallet process. The wallet remains the point where the person can inspect and approve or reject a later transaction or signature request.

Connection permission therefore does not give a site standing permission to sign future actions. Rabby exposes connection requests through notification, popup and full-page surfaces, then presents later requests as separate decisions.

The pre-sign preview makes the asset effect visible

Before signing, Rabby presents an expected balance-change preview alongside a potential-risk scan. This is especially useful for DeFi calls, where contract calldata alone may not communicate the intended token movement, approval or swap outcome.

The preview is decision support rather than a guarantee that an interaction is safe or that chain state will remain identical until execution. The user still controls the signature, and a signed transaction must still be submitted and included before it has an onchain effect.

A user-facing wallet differs from a security engine or revocation tool

Rabby is the wallet used by the person authorising an EVM action, not a transaction-security API another wallet or application embeds. That makes its scan and preview a direct consent-time safeguard rather than a behind-the-scenes screening service for many products.

Blockaid is the contrasting infrastructure-style security engine, while Revoke.cash addresses allowances that already exist. Rabby concentrates on evaluating a requested interaction before it creates an onchain effect, within its browser-wallet and EVM scope.