Response Headers

As we are proxying the API requests, we decorate this response with some of our own custom headers, most notable are the actual EOS producer and corresponding API host that served the request.

Each response also contains the geographic location of our application node that served the request, along with the fetch time from the producer API and the total time of the request.

We have also enabled HTTP persistent connections, so that multiple requests can be served as efficiently as possible.

Improving Reliability

We created the proxy to help developers and to improve the user experience for EOS dApps. Within our app, we have implemented many features that trigger transparently to improve the response success rate and speed.

For example, if the initial proxied producer returns a non-standard nodeos error, the proxy will auto retry the request using a different producer.

Within our producer selection algorithm, we deprioritise producer API hosts that start to return failures or begin to respond slowly.

With these safeguards in place, we have dramatically increased the percentage of successful requests which should make any app that relies on EOS chain data much more reliable.

We also collect metrics for every call to our proxy and we want to use this data with our fellow block producers to help improve API performance and reliability across the EOS network.

Geo-DNS Routing

It's imperative that a proxy service is as fast as possible. We have deployed application nodes around the globe and utilise Geo-DNS routing to reduce request latency for calls to the proxy.

Get in touch with us

About EOS Node Tools

This microsite is maintained by Block Matrix who are a paid standby block producer for the EOS network. We are a dedicated team of blockchain nerds who get excited by large scale infrastructures and fancy ascii art.