JSON RPC Caching Proxy reduces latency and optimizes costs

How does blockchain feel without JSON-RPC protocol during IFO?

1. Normal state
The calm before the storm
2. Hello, 50 000 RPS
IFO starts getting your infrastructure under siege
3. Nodes slow down
The node is shocked and users leave unsatisfied

Apply a tool that deals with any RPS load by applying JSON RPC methods

Downtime for platforms and apps that use blockchain as a core technology is always costly. You may lose millions in seconds of delay while nodes are stuck.

Here at Dysnix, we’ve saved our clients multiple times from overflowing traffic by balancing their nodes and cloud resources manually until we decided to use JSON-RPC protocol and solve this problem. We’ve tested it in production and made it customizable for any sized project.

Now, we encourage you to try the JSON RPC Caching Proxy solution that can reduce latency and deal with any load, autoscale your nodes without any sign for your audience, and even cut your cloud bill.

Try our JSON RPC example to make your nodes 100% available

1.Dealing with millions of RPS
Automatic proactive scaling for any load
2.99.99% of infrastructure uptime
Constantly low latency, even for global projects
3.No effect on user experience
Your nodes won’t even mention any traffic spikes

Under the hood: Tools inside

We made our JSON RPC Caсhing Proxy using the top-notch technologies available for blockchain and cloud technologies:

JSON RPC Caching Proxy removes latency spikes

JSON RPC Caching Proxy saves costs and guarantees 99.99% uptime

Reduce RPS by
Reduce costs by

Improve your infrastructure with the JSON-RPC methods of Caching Proxy

Try now

Questions and answers

If you don’t find your issue here, don’t hesitate to contact us for any consultations.

What is JSON-RPC used for?

JSON-RPC is widely used for access to the application with the remote procedure call (RPC) and using JSON to define the parameters you want to get. It’s widely used because of its benefits compared to REST and other standards: platform-agnostic type, quick development and simple handling, explainable results, and straightforward data transfer. Here you can find the typical JSON-RPC example.

Is JSON-RPC still used?

Yes, it’s still quite popular among developers. It’s widely used in blockchain and microservices, where quick communication between applications and other structural blocks of infrastructure is essential. The variety of JSON-RPC methods can be attributed to one of the JSON-RPC 1.0 or 2.0 versions.

What is JSON-RPC response?

When the call is initiated, the server has to send a Response, except for Notifications. The typical JSON-RPC response is a JSON Object that has a few members: an ID (that’s the same as in Request Object), jsonrpc specifying “2.0” version, error and result, which are mutually exclusive.


No, you can’t consider JSON-RPC protocol an API. But it can be incorporated into an API as a part responsible for the connection. Our JSON RPC Caching Proxy is an excellent example of this implementation.

How JSON RPC Caching Proxy works in simple words

The simplest JSON-RPC example from real life is a kind of information kiosk at the train station that can print tickets, too. Passengers must contact the information kiosk first, and only then they will be distributed for their nodes-as-platforms to work with the infrastructure further. The JSON-RPC protocol works fast and well with all requests to nodes, not delaying any of them.