Cowrie Research

rabby

3 min read

Rabby

  • Name: Rabby
  • URL: https://rabby.io/
  • Category: multichain wallet / EVM wallet-control-plane infrastructure / DeFi transaction-signing and simulation layer / open-source wallet client stack
  • Tags: ethereum-ecosystem
  • Summary: Rabby is an EVM wallet-control stack, not just a browser extension. The useful primary-source evidence is the combination of the extension repo, shared mobile monorepo, package inventory, and integration guidance: Rabby is really a user-side policy and transaction-interpretation layer that sits between dapps and onchain execution. That is why the note matters.
  • What it does:
    • Ships an open-source browser wallet for Ethereum and EVM networks aimed at DeFi users
    • Maintains separate desktop and mobile clients in addition to the main extension, according to the public GitHub organization
    • Publishes explicit dapp-integration guidance around injected-provider detection and how sites should present Rabby alongside MetaMask-style flows
    • Exposes a concrete extension architecture with separate background, content-script, page-provider, and UI contexts for wallet logic and dapp request handling
    • Maintains a shared monorepo of wallet packages that includes universal providers, storage utilities, address/keyring services, and hardware-keyring modules for devices such as Ledger, Trezor, Keystone, and OneKey
    • Appears to operate first-party swap, bridge, and security-engine modules in the extension package inventory, alongside Safe-related dependencies and other wallet-infrastructure components
  • Key claims:
    • The homepage positions Rabby as a go-to wallet for Ethereum and EVM, but the public code surface is broader than that marketing frame
    • The GitHub organization shows separate browser, desktop, and mobile clients, which makes Rabby look like a maintained wallet stack rather than a single extension shell
    • The extension README says Rabby aims to provide a more secure multi-chain experience, and the implementation details make that security claim concrete through simulation, provider handling, and policy layers rather than branding alone
    • The integration guidance is unusually useful because it shows Rabby thinking like infrastructure: it cares how dapps detect and route to the wallet before any signature is requested
    • The extension architecture notes describe controller boundaries for wallet logic and provider handling, which makes the product easier to catalog as wallet middleware rather than just wallet UX
    • The extension package.json shows first-party modules such as @rabby-wallet/rabby-security-engine, @rabby-wallet/rabby-bridge, @rabby-wallet/rabby-swap, @rabby-wallet/page-provider, and Safe-related dependencies, reinforcing that Rabby is a broader control stack than a signing popup
  • Whitepaper: No canonical Rabby whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official site plus the public GitHub organization, extension repository, shared monorepo, and package metadata; see ../whitepapers/rabby-primary-sources-2026-04-28.md.
  • Sources:

Internal linkages

Governance / control risk

  • The leverage sits in provider injection, chain defaults, simulation quality, warning heuristics, and which routes or security checks Rabby makes easiest to accept.

  • So this is not neutral wallet chrome. It is user-side policy software sitting in front of execution.

  • Last reviewed: 2026-05-31 UTC

Graph View

Backlinks