[ERC Registry EPIC] Phase 2: Integrate validation through the contract call API and address edge cases to enhance accuracy.

[quiet-node]

Problem

After Phase 1, the ERC indexing tool can now detect ERC contracts and categorize them into ERC-20 and ERC-721. However, the categorized contracts only include the contract ID and EVM address, lacking other essential information such as name, symbol, and decimals.

Solution

Implement a new mechanism to make calls to the mirror node to retrieve the necessary information.

A better and improved schema for an ERC20 should include detailed token information

{
    "address": "0x....",  // Address of the ERC20 contract/token
    "contractId": "0.0.x",  // contract id of the ERC20 contract/token
    "name": "...",
    "symbol": "...",
    "decimals": x,
    "totalSupply": "..."
  }

A better and improved schema for an ERC721 should include detailed token information

{
    "address": "0x....",  // Address of the ERC20 contract/token
    "contractId": "0.0.x",  // contract id of the ERC20 contract/token
    "name": "...",
    "symbol": "...",
  }

Alternatives

No response

Tasks

Preview Give feedback

1. [ERC Registry] Phase 2: Utilize contract call mirror node API for enhanced accuracy and to retrieve token details. #1059
   enhancement +1
   
2. [ERC Registry] Phase 2: Allow the tool to run against localnet #1070
   enhancement +1
   
3. [ERC Registry] Phase 2: Add a suite of acceptance test to test the tool against localnode #1065
   enhancement +1
   
4. [ERC Registry] Phase 2: Generate final registry JSON files #1074
   enhancement +1
   
5. [ERC Registry] Phase 2: Add an option to execute the indexing tool as a GitHub dispatch workflow #1081
   internal +1