Current RPC and Decentralization Status
Published 7/24/2026, 3:35:05 AM
As of July 2026, research indicates that Rabby Wallet has not implemented RPC changes that force users toward centralized alternatives. Instead, Rabby maintains a highly flexible architecture that allows users to manually configure their own node connections, preserving user sovereignty and decentralization.
Current RPC and Decentralization Status
Rabby continues to prioritize a non-custodial, open-source model. While some technical friction has been noted with specific third-party RPC providers, the wallet's core settings still empower users to bypass centralized infrastructure.
| Feature | Status (July 2026) | Impact on Decentralization |
|---|---|---|
| Custom RPC Support | Active | Users can add/modify RPC URLs for 240+ chains, preventing lock-in to providers like Infura [Source: https://x.com/Rabby_io/status/1604092212450660353]. |
| Key Management | Front-end Only | Private keys are stored locally and never transmitted to Rabby's back-end [Source: https://medium.com/rabby-wallet/release-announcement]. |
| Open Source License | MIT Licensed | Fully open-source code allows for community auditing of all infrastructure calls [Source: https://rugdoc.io/wiki/rabby-wallet-guide]. |
| Monetization | 0.25% Swap Fee | Introduced in 2024; centralizes revenue but does not affect RPC or custody [Source: https://rabby.io/updates/2024]. |
Analysis of Potential Centralization Risks
The research identified several key areas where users might perceive a shift, though these are largely technical or economic rather than structural:
- Technical Friction vs. Policy: Recent developer logs (e.g., GitHub Issue #2810) show that some custom RPCs (like Tenderly VNET) struggle with balance displays and gas estimation [Source: https://github.com/RabbyHub/Rabby/issues/2810]. This is a technical limitation of the RPC providers themselves, not a forced move by Rabby to centralize its node infrastructure.
- User Sovereignty: Rabby remains a "front-end only" tool. Because it does not construct transactions on its own back-end but simulates them before the user signs via their chosen RPC, it maintains a higher degree of censorship resistance compared to wallets with more opaque default settings.
- Market Positioning: While competitors like MetaMask have faced criticism for default RPC settings that may track user data, Rabby's transparency and simulation features continue to attract "power users" who prioritize decentralization.
Conclusion
There is no evidence that Rabby is pushing users toward centralized RPCs. The wallet remains one of the most decentralized options for EVM users, offering full control over node connections. The primary challenge for users is not a lack of choice, but the technical complexity of maintaining stable connections with decentralized or custom RPC providers. Specific data on user migration metrics following recent updates remains unavailable in current research.