<?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: Pranjal Prashar</title>
    <description>The latest articles on Developers Forum for XinFin XDC Network by Pranjal Prashar (@pranjal_prashar_be5b9585f).</description>
    <link>https://www.xdc.dev/pranjal_prashar_be5b9585f</link>
    <image>
      <url>https://www.xdc.dev/images/QlPbWnKj8y-DIjaez6wD5Rzo0zS2M6h9XxTUJQSL5qM/rs:fill:90:90/mb:500000/ar:1/aHR0cHM6Ly93d3cu/eGRjLmRldi91cGxv/YWRzL3VzZXIvcHJv/ZmlsZV9pbWFnZS8z/NjkxL2M4ZTQ5Mzgz/LWQwMmUtNDhhZi1i/YmY3LTljNjNjNjUz/NjZkYy5wbmc</url>
      <title>Developers Forum for XinFin XDC Network: Pranjal Prashar</title>
      <link>https://www.xdc.dev/pranjal_prashar_be5b9585f</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://www.xdc.dev/feed/pranjal_prashar_be5b9585f"/>
    <language>en</language>
    <item>
      <title>Subgraph issue with WeFi integration</title>
      <dc:creator>Pranjal Prashar</dc:creator>
      <pubDate>Wed, 04 Dec 2024 11:05:20 +0000</pubDate>
      <link>https://www.xdc.dev/pranjal_prashar_be5b9585f/subgraph-issue-with-wefi-integration-2ijf</link>
      <guid>https://www.xdc.dev/pranjal_prashar_be5b9585f/subgraph-issue-with-wefi-integration-2ijf</guid>
      <description>&lt;p&gt;We have been using Subquery indexing service for xdc subgraph. They had some problems with it, we are following up with them.&lt;/p&gt;

&lt;p&gt;Initially we were running graph node in our own servers. &lt;a href="https://github.com/XinFinOrg/XDC-Graph-Node"&gt;https://github.com/XinFinOrg/XDC-Graph-Node&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We had some issues:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;When deploying changes to the codebase or adding new contracts, it syncs from starting and all data is only available when it syncs till latest block. As our protocol have been for a long time in XDC network, for a very long period we experienced data outage. Switching to Subquery solved this as indexer services serves from previous release until latest release is  synced to latest block.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Computing and Storage resources:&lt;br&gt;
We need some suggestion on  what should be the server configuration for an ec2 instance in Amazon AWS. In t2.medium instance, the indexing process was slow. &lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;In general we don't run indexer on our own, we use thegraph, goldsky etc. &lt;/p&gt;

&lt;p&gt;Any suggestions to fix this ?&lt;/p&gt;

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