Introducing eRPC - an open-source fault-tolerant EVM RPC proxy with reorg-aware permanent caching.
Why? - To have higher reliability and lower RPC costs.
Let's dive into first release features π
Also in 0.5.0:
eRPC answers eth_chainId, net_version and other node-info calls itself, without a call to a node.
A node that fails one method can be skipped for that method only.
WebSocket is opt-in: server.webSocket.enabled
https://t.co/a0xmvIp82T
eRPC 0.5.0 is out, with WebSocket support.
Subscribe to new blocks, logs and pending transactions over ws://, on the same port as HTTP. Clients on the same filter share one subscription per node.
74 changes: 18 features and 35 fixes, from 8 contributors.
eRPC can cut over 50% of your eth_call traffic to RPC providers.
It bundles calls for the same block into one Multicall3 request.
On 22 minutes of real BNB Chain traffic: 62.5% fewer upstream requests, same answers.
eth_blockNumber p99 fell ~95% from 215-461 ms to 10-20 ms
eth_blockNumber errors fell ~96% from ~2.6K to ~100 a day
Merged to main: https://t.co/DcYLJxLazx
eRPC now sends 98% fewer eth_blockNumber calls to RPC providers.
Calls per day dropped from 40.48M down to 0.69M, comparing 7 days before and after this update.
Latency and error rates also dropped...
Monad's MIP-16 eth_query methods are live on Goldsky Edge RPC.
eth_queryBlocks
eth_queryTransactions
eth_queryLogs
eth_queryTraces
eth_queryTransfers
JSON-RPC and gRPC. Conformance suite: 236/236 against prod.
New in eRPC: plug in @goldskyio's gRPC cache.
Historical blocks, logs, txs and receipts come fast from data Goldsky has already indexed, not from nodes that can return missing or wrong results.
22 chains, one connector:
https://t.co/5FKw0cGwqP
We just shipped Boost, a free (for limited time) CDN that sits in front of your existing RPC provider and cuts your bill (just swap the URL).
Check it out: https://t.co/3U5byk7J0H
Some of the best things you ship are often invisible.
RPCs are one of those fundamental pieces of tech every company in web3 uses. The reliability on stable and consistent RPC connections is crucial to @SafeLabs_ products.
We recently moved to @ERPC from HA Proxy and the results have been clear. Much lower latency and it impacts every user.
What does this mean for the user? Faster transactions, lower failures and consistent UX using Safe Wallet and Safe Mobile πͺπ½
. @erpc release 0.1.0 is here π§βπ
Few important highlights:
- Hundreds of data quality improvements (e.g. latest block and tip of chain nuances)
- Unified and improved selection policy so you have complete control over which RPC nodes to use and when (e.g. block lag, response time latency, RPC costs)
- More metrics and visibility into why a node was selected and for how long it was used
Today we're officially part of Goldsky.
eRPC stays open-source and actively maintained. That was always the deal.
Here's the journey that got us here π§΅