[ERC Registry EPIC] Phase 3: Further features

[quiet-node]

Problem

Currently, the ERC Registry project has an MVP capable of indexing the network, detecting ERC-20 and ERC-721 tokens, and writing the records to the registry. However, additional features could enhance the tool and make it more versatile.

Solution

Implement new enhancements and features based on user feedback to improve the tool.

Tasks

Preview Give feedback

1. [ERC Registry] Phase 3: address team feedback on the first MVP #1111
   3 of 3
   Epic enhancement +2
   
2. [ERC Registry] Phase 3: Modify the workflow script to also create a PR target MNE repo #1128
   enhancement +1
   
3. [ERC Registry] Phase 3: Add Support for Scanning a Dynamic Number of Contracts #1131
   enhancement +1
   
4. [ERC Registry] Phase 3: Add an option to detect ERC contracts without updating the registry. #1133
   enhancement +1
   
5. [ERC Registry] Phase 3: Implement a sorting mechanism to sort the ERC records to allow back filling #1130
   enhancement +1
   
6. [ERC Registry] Phase 3: Add functionality for bytecode storage.

[quiet-node]

The proposed functionality to store bytecode in the registry may not be practical to implement, as it does not provide additional benefits and could negatively impact performance. Bytecodes are typically large, and the registry contains thousands of contracts. Including bytecode for each contract would significantly increase the size of the registry files, resulting in longer load times for dependent applications. Given these drawbacks, this feature will be temporarily removed from the roadmap.