There are currently multiple methods being used to fulfill the ABI parameter within the dApp. This inconsistency can lead to maintainability issues and unnecessary complexities. To streamline development and reduce dependencies, it's suggested to adopt a single standard method for handling ABIs across the entire application. The method used in the referenced code avoids bringing ABIs into internal folders and should be applied universally.
Requirements
[ ] Review all instances where the ABI parameter is being handled differently across the dApp.
[ ] Standardize the ABI handling by adopting the method used in the referenced code, which minimizes the need for storing ABIs in internal folders.
[ ] Refactor existing implementations to align with this new standard.
Additional Information
This standardization will simplify the codebase and reduce the risk of inconsistencies or errors related to ABI management.
Ensure that the transition to the new standard is well-documented and that all relevant team members are informed of the change.
Refactor Request
Description
There are currently multiple methods being used to fulfill the ABI parameter within the dApp. This inconsistency can lead to maintainability issues and unnecessary complexities. To streamline development and reduce dependencies, it's suggested to adopt a single standard method for handling ABIs across the entire application. The method used in the referenced code avoids bringing ABIs into internal folders and should be applied universally.
Requirements
Additional Information
https://github.com/blockful-io/external-resolver-dapp/blob/d7a67ed7072bc69790281ffb87775b318a136a09/lib/utils/blockchain-txs.ts#L85
Possible Solution
Audit the current ABI handling methods across the project and refactor them to use the approach demonstrated in the provided code snippet.