Using eRPC to speed up indexing and increasing resiliency and data integrity of Sablier's RPC stack #162
Replies: 3 comments 1 reply
-
|
Hey @kasrakhosravi, thanks for posting this — I've opened an issue to try out eRPC in our Indexers: Will let you know our feedback once we try it. |
Beta Was this translation helpful? Give feedback.
-
|
hey @kasrakhosravi, you mentioned an aggregator endpoint in the OP. What's the URL for that? I couldn't find anything on your landing page (erpc.cloud). |
Beta Was this translation helpful? Give feedback.
-
|
hey @PaulRBerg. the aggregator endpoint is a premium service we are offering to our design partner customers. should I prepare an api key for you guys to start testing? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
gm frens :)
I think eRPC can be a useful for Sablier's indexing (or other domains such as frontend). The main benefits probably can be summarized as below:
The way you can adopt this is to:
Either use the open-source version and deploy it in your own infra (k8s, Docker, Railway, etc.). You can configure all your RPC providers into the config
Or use our aggregator endpoint where we give you an endpoint for any evm chain you need access to; and behind the scenes it gets benefit from erpc to offer the sweet spot of latency, data integrity, resiliency and cost.
Beta Was this translation helpful? Give feedback.
All reactions