<?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: CoinCow Art</title>
    <description>The latest articles on Developers Forum for XinFin XDC Network by CoinCow Art (@coincow_art_a9fac6bf88081).</description>
    <link>https://www.xdc.dev/coincow_art_a9fac6bf88081</link>
    <image>
      <url>https://www.xdc.dev/images/-hip1bkCWpTRifKH_aIb5_BO8-LSL7yi27Xh1DirPjI/rs:fill:90:90/mb:500000/ar:1/aHR0cHM6Ly93d3cu/eGRjLmRldi91cGxv/YWRzL3VzZXIvcHJv/ZmlsZV9pbWFnZS82/MDUvZmFiMjYwNzUt/YmVmYi00OGVmLThm/NDAtYWIyOWQzMzgx/Njc0LnBuZw</url>
      <title>Developers Forum for XinFin XDC Network: CoinCow Art</title>
      <link>https://www.xdc.dev/coincow_art_a9fac6bf88081</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://www.xdc.dev/feed/coincow_art_a9fac6bf88081"/>
    <language>en</language>
    <item>
      <title>[Proposal] Add functionality to check if a specific holder address holds a specific token on the BlocksScan API.</title>
      <dc:creator>CoinCow Art</dc:creator>
      <pubDate>Thu, 29 Feb 2024 01:06:07 +0000</pubDate>
      <link>https://www.xdc.dev/coincow_art_a9fac6bf88081/add-functionality-to-check-if-a-specific-holder-address-holds-a-specific-token-on-the-blocksscan-api-3gk8</link>
      <guid>https://www.xdc.dev/coincow_art_a9fac6bf88081/add-functionality-to-check-if-a-specific-holder-address-holds-a-specific-token-on-the-blocksscan-api-3gk8</guid>
      <description>&lt;p&gt;I would like a search feature in the BlocksScan API to determine if a holder address holds a particular token.&lt;/p&gt;

&lt;p&gt;If that feature were added, it would enable the development of various web services. Particularly, by adding a function to confirm whether someone holds an NFT on the web, it would be possible to create web pages that only holders can view, and it would also enable the development of games centered around holders' NFTs.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.xdc.dev/images/ccLrrgyU-c6wICaz-WPG9aBF8xH_ejZYnoM3k52CAUA/w:880/mb:500000/ar:1/aHR0cHM6Ly93d3cu/eGRjLmRldi91cGxv/YWRzL2FydGljbGVz/LzU5dXYxMnhteWFt/Z2VkaXBuOGN0LnBu/Zw" class="article-body-image-wrapper"&gt;&lt;img src="https://www.xdc.dev/images/ccLrrgyU-c6wICaz-WPG9aBF8xH_ejZYnoM3k52CAUA/w:880/mb:500000/ar:1/aHR0cHM6Ly93d3cu/eGRjLmRldi91cGxv/YWRzL2FydGljbGVz/LzU5dXYxMnhteWFt/Z2VkaXBuOGN0LnBu/Zw" alt="Image description" width="880" height="398"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Current Situation&lt;/strong&gt;:&lt;/p&gt;

&lt;p&gt;The API currently has a function to retrieve a list of tokens based on the token type and holder address. However, there is no function to determine whether a specific token is held.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Challenges&lt;/strong&gt;:&lt;/p&gt;

&lt;p&gt;Without this function, developers need to implement the following tasks on their own:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Call the API to retrieve the token holding list&lt;/li&gt;
&lt;li&gt;Search for a specific token in the holding list&lt;/li&gt;
&lt;li&gt;Determine whether the token exists
These tasks can be a burden for developers and can lead to code complication.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Additionally, if there is a wallet address holding hundreds of tokens, such as NFTs, the API needs to be accessed page by page using a while loop due to the 50 token limit per page. This can be avoided with the proposed function, which can reduce the number of API accesses.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Benefits&lt;/strong&gt;:&lt;/p&gt;

&lt;p&gt;Adding this function will provide the following benefits:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Reduced workload for developers&lt;/li&gt;
&lt;li&gt;Simplified code&lt;/li&gt;
&lt;li&gt;Improved development efficiency&lt;/li&gt;
&lt;li&gt;Reduced number of API accesses&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>proposal</category>
      <category>blocksscan</category>
      <category>api</category>
    </item>
  </channel>
</rss>
