<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Developers Forum for XinFin XDC Network: John Grimsey</title>
    <description>The latest articles on Developers Forum for XinFin XDC Network by John Grimsey (@jg).</description>
    <link>https://www.xdc.dev/jg</link>
    <image>
      <url>https://www.xdc.dev/images/zM209Cbcyfik8ai0nMlsJRlApjI6lxfm_qWGrtSkpGA/rs:fill:90:90/mb:500000/ar:1/aHR0cHM6Ly93d3cu/eGRjLmRldi91cGxv/YWRzL3VzZXIvcHJv/ZmlsZV9pbWFnZS8y/MDE2L2E3YWJhNGY4/LWQxZmEtNGI5Yy05/NDg0LWQ4OTYwZGQ5/NjMxZi5wbmc</url>
      <title>Developers Forum for XinFin XDC Network: John Grimsey</title>
      <link>https://www.xdc.dev/jg</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://www.xdc.dev/feed/jg"/>
    <language>en</language>
    <item>
      <title>Tooling request: surface RPC node(s) health</title>
      <dc:creator>John Grimsey</dc:creator>
      <pubDate>Thu, 21 Dec 2023 08:53:37 +0000</pubDate>
      <link>https://www.xdc.dev/jg/tooling-request-surface-rpc-nodes-health-cjm</link>
      <guid>https://www.xdc.dev/jg/tooling-request-surface-rpc-nodes-health-cjm</guid>
      <description>&lt;h2&gt;
  
  
  Synopsis
&lt;/h2&gt;

&lt;p&gt;We rely on RPC nodes to work with the XDC and Apothem networks. We can think of them as dependencies of our dapps.&lt;/p&gt;

&lt;p&gt;When consuming vendor APIs, it is often quite normal to be able to monitor the health and status of these dependencies. It is most normal in the world of GCP and AWS.&lt;/p&gt;

&lt;h2&gt;
  
  
  Tooling request
&lt;/h2&gt;

&lt;p&gt;I would like to request the build of some tooling which enables us to monitor the current state of RPC nodes for the XDC and Apothem networks. &lt;/p&gt;

&lt;p&gt;chainlist.org provides some useful information but it doesn't necessarily contain the latest list of RPC nodes available to use. Support in Discord has been helpful during the Apothem upgrade, but we must rely on the availability of certain users and their knowledge of the current state.&lt;/p&gt;

&lt;h3&gt;
  
  
  RPC health check endpoints
&lt;/h3&gt;

&lt;p&gt;One good solution would be health endpoints for RPC nodes. &lt;/p&gt;

&lt;h3&gt;
  
  
   Aggregate status
&lt;/h3&gt;

&lt;p&gt;Perhaps even better would be a service that always knows about the available RPC nodes for each network. An RPC registry service. This could list all available nodes and their respective health.&lt;/p&gt;

&lt;p&gt;This would facilitate the use of a round-robin approach for building app-resilience. It might also aid in handling and surfacing errors to users in a deterministic manner.&lt;/p&gt;

&lt;p&gt;Thanks for reading&lt;br&gt;
John&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
