RPCh Beta Public Release
After several months of Alpha testing, RPCh has reached a level of long-running stability and performance capable of supporting a host of wallets and their users. On top of this newfound power, RPCh now also comes with MEV protection, saving users money they would have otherwise lost to MEV exploits, all while still offering the strongest protection on the market against IP address and metadata harvesting from your RPC provider or any other third parties.
You can see how RPCh compares against VPNs or Proxies on our site and how it compares against other RPC providers in this article. This blog will otherwise cover what’s new with RPCh Beta and how you can still use RPCh for free if you are quick enough (offer ends October 31st).
MEV Protection
RPCh Beta leverages PropellerHeads to optimize your transactions.
By using PropellerSolver, your transactions are routed through the best possible route through multiple liquidity sources, giving you the best price and removing any chance of your transactions being backrun.
On top of this, the PropellerRPC sends requests directly to all major block builders and makes your transactions invisible to searchers. This protects you from all frontrunning, sandwich and even multi-block attacks.
It is worth noting that this is only available for transactions made on the mainnet. If you do not wish to use MEV protection, you can remove it from your setup by editing your docker command or even switch to a different MEV provider of your choice. PropellerHeads is the default setup, but it can always be altered. You can see how in our docs here.
Stability & Performance
A large part of RPCh Beta’s stability is derived from the latest HOPR release: Dufour. The release is extremely stable and has removed many of the issues inherited from js-libp2p, which had been previously passed onto RPCh Alpha.
But on top of using a better HOPR release, RPCh Beta also comes with retransmission and availability monitoring. These are features that ensure your requests are retried and re-routed through new, reliable nodes until they are successfully transmitted.
Default Chains: Ethereum, Gnosis, zkEVM
RPCh has added three new default chains, allowing you to set up RPCh on three separate chains through just a single click on our UI.
The new default RPC endpoints are hosted by HOPR on Ethereum mainnet, Gnosis Chain and Polygon zkEVM. Although all of the default nodes are currently hosted by HOPR in partnership with Gateway, these nodes will become more decentralized in the near future.
If you don’t want to use any of our endpoints, you can always choose your own custom provider on any EVM chain (including L2s). This is absolutely fine; you can see how to do so in our docs. All of the privacy and value-adding services packaged within RPCh are delivered as middleware sitting in between your wallet and the RPC provider it communicates with, so you can choose to use RPCh with any EVM chain, RPC provider or wallet of your choice while still benefiting from everything RPCh has to offer.
Use RPCh Beta for Free
With the release of RPCh Beta, RPCh is now a paid service, but luckily, you can still use it for free if you sign up for RPCh before the 31st of October 2023. To use RPCh for free, you simply need to:
1.) Visit degen.RPCh.net
2.) Select the DEGEN package
3.) Sign in with your wallet
4.) Enter promo code: FREEPRIVACY
5.) Install RPCh via Docker
You can view a complete breakdown of how to do all of this step-by-step on our documentation here.
Sebastian Bürgel,
HOPR Founder
Website: https://rpch.net
Run RPCh Beta: https://degen.rpch.net/
Twitter: https://twitter.com/RPC_h_
Discord: https://discord.gg/VRyTQTNBTy
Powered by HOPR: https://hoprnet.org/
If you’re an investor click here: scale.RPCh.net
If you’re a wallet, click here: https://rpch.net/wallets
