Cowrie Research

rabby-primary-sources-2026-04-28

3 min read

Rabby primary-source snapshot

Fetched: 2026-04-28 UTC

1) Official homepage

Source: https://rabby.io/

Selected signal from the official site title:

Rabby Wallet | Your Go-to Wallet for Ethereum and EVM

Additional signals from the source:

  • The homepage is concise and mostly acts as a top-level brand surface rather than a deep technical source
  • Even this minimal framing is enough to anchor Rabby as explicitly EVM-focused rather than a generic multichain wallet across every chain family

2) GitHub organization

Source: https://github.com/RabbyHub

Selected excerpts/signals from the public org page:

A browser plugin for DeFi users

The game-changing wallet for Ethereum and all EVM chains

rabby desktop application, for web3 users

rabby mobile application(iOS & Android), for web3 users

Additional signals from the source:

  • The org page is one of the clearest current primary sources because it immediately shows Rabby operating across browser, desktop, and mobile clients
  • The pinned repos materially broaden the categorization beyond a simple extension brand

3) Extension README

Source: https://raw.githubusercontent.com/RabbyHub/Rabby/develop/README.md

Selected excerpts from the official repo:

Rabby Wallet is an open-source browser plugin for the DeFi ecosystem, providing users with a better-to-use and more secure multi-chain experience.

To help dapp developers support and integrate Rabby Wallet more easily, we recommend using our integration solution that has almost NO development cost and does not introduce any uncertainty

Additional signals from the source:

  • The README is useful because it treats Rabby not only as an end-user wallet but also as an integration target that dapps should explicitly accommodate
  • The provider-detection guidance is a good clue that Rabby is operating as an access layer inside the EVM wallet ecosystem, not only as a retail wallet app

4) Extension architecture notes

Source: https://raw.githubusercontent.com/RabbyHub/Rabby/develop/README.md

Selected excerpts from the official repo:

background.js handles all async requests and encryption tasks.

providerController handles requests from pages (dapp requests).

pageProvider.js mounts ethereum to window.

The content-script will send a message to background with runtime.connect.

Additional signals from the source:

  • The README provides a concrete mental model for how Rabby handles injected-provider traffic, wallet logic, and UI separation
  • This makes Rabby easier to catalog as wallet infrastructure and client architecture rather than just wallet marketing

5) Shared mobile/core monorepo

Source: https://raw.githubusercontent.com/RabbyHub/rabby-mobile/develop/README.md

Selected excerpts from the official repo:

This monorepo is a collection of packages used across multiple RabbyHub clients (e.g. Rabby, rabby-mobile).

@rabby-wallet/eth-keyring-gnosis

@rabby-wallet/eth-keyring-keystone

@rabby-wallet/eth-keyring-ledger

@rabby-wallet/eth-keyring-onekey

@rabby-wallet/eth-keyring-trezor

@rabby-wallet/universal-providers

@rabby-wallet/service-keyring

Additional signals from the source:

  • The package inventory is a strong clue that Rabby is maintaining a reusable wallet stack rather than isolated app clients
  • Hardware-keyring modules and shared provider/keyring services suggest a wallet-control-plane orientation

6) Extension package inventory

Source: https://raw.githubusercontent.com/RabbyHub/Rabby/develop/package.json

Selected excerpts/signals from the official repo:

“description”: “A browser plugin for DeFi users”

@rabby-wallet/rabby-security-engine

@rabby-wallet/rabby-bridge

@rabby-wallet/rabby-swap

@rabby-wallet/page-provider

@safe-global/protocol-kit

Additional signals from the source:

  • The public package list is especially informative because it exposes internal product breadth that the homepage does not spell out
  • The combination of security engine, bridge, swap, provider, and Safe-related dependencies suggests Rabby is operating a richer transaction and wallet middleware layer than a simple signer-only extension

Notes

  • Rabby appears best cataloged as multichain wallet / EVM wallet-control-plane infrastructure / DeFi signing and simulation layer / open-source client stack.
  • No canonical whitepaper or litepaper surfaced in this pass.
  • The strongest categorization clue is that the public repo surface shows Rabby spanning browser, desktop, mobile, provider injection, keyring services, and transaction modules rather than existing only as a single extension UX.

Graph View