Cowrie Research

rabbyhub-primary-sources-2026-08-08

3 min read

RabbyHub primary-source snapshot

Fetched: 2026-08-08 UTC

1) Rabby homepage / official product framing

Source: https://rabby.io/

Selected excerpts from the official site metadata:

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

The game-changing wallet for Ethereum and all EVM chains

Additional signals from the source:

  • The official site is sparse, but it cleanly anchors the first-party brand and download surface
  • This is useful for the entity split because the question is not whether Rabby exists as a product; it is who ships and steers that product surface in practice

2) RabbyHub GitHub organization / named operator surface

Source: https://api.github.com/orgs/RabbyHub

Selected excerpts from the official GitHub API response:

“login”: “RabbyHub”

“name”: “Rabby”

“blog”: “https://rabby.io”

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

Additional signals from the source:

  • The organization API is one of the clearest first-party proofs that a named operator boundary exists above the wallet artifact itself
  • The org points directly at the official site and describes the operator as more than a one-off repo

3) Main Rabby repository / product and integration guidance

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

Selected excerpts from the official repository:

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.

On your connection page, display both connection buttons for “MetaMask” and “Rabby Wallet” when the “Ethereum” object is detected.

You can refer to debank.com for the final display effect.

Additional signals from the source:

  • The README is unusually useful because it shows RabbyHub shaping how third-party dapps present wallet choices before a signature request even happens
  • The debank.com reference is a clue that Rabby’s operator boundary is tied to a broader first-party account and interface shell rather than only a browser extension popup

4) Extension architecture / request and encryption control plane

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

Selected excerpts from the official repository:

background.js Handles all async requests and encryption tasks.

providerController Handles requests from pages (dapp requests).

pageProvider.js … mounts ethereum to window.

Additional signals from the source:

  • This makes the practical control surface legible: provider injection, request handling, and wallet mediation all sit inside one operator-maintained software path
  • That is exactly the kind of surface where a separate company/entity note adds analytical value

5) Extension package graph / first-party module composition

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

Selected excerpts from the official package manifest:

“@rabby-wallet/page-provider”

“@rabby-wallet/rabby-action”

“@rabby-wallet/rabby-api”

“@rabby-wallet/rabby-bridge”

“@rabby-wallet/rabby-security-engine”

“@rabby-wallet/rabby-swap”

“@rabby-wallet/staking-sdk”

“@rabby-wallet/widgets”

Additional signals from the source:

  • The package inventory shows the operator boundary includes simulation, security interpretation, bridge and swap routing, wallet actions, widgets, and service composition rather than only raw signing
  • This is strong evidence that companies/rabbyhub is useful as a control-surface note distinct from projects/rabby

6) Multi-client operator surface

Source: https://github.com/RabbyHub

Selected excerpts/signals from the official organization page:

  • Public repositories include Rabby, rabby-mobile, rabby.io, rabby-bridge, rabby-api, and rabby-swap
  • The public mobile repository is described as rabby mobile application(iOS & Android), for web3 users

Additional signals from the source:

  • The named operator boundary spans browser wallet, mobile clients, first-party site, routing modules, and adjacent APIs
  • That makes the control question broader than what can the extension sign?

Notes

  • This snapshot was created to support a new companies/rabbyhub note and a project/company split refresh for Rabby.
  • The useful split is between projects/rabby as the wallet product surface and companies/rabbyhub as the named operator organization that ships releases, curates transaction interpretation and route modules, and shapes how dapps and users meet Rabby in practice.

Graph View