Feature Request: ABI Parsing and Dynamic Event Data Handling at Block Height

[jac18281828]

Description

We need to enhance our system by implementing the following functionality:

1. Script to Track Upgrades and ABI Changes:

   • Develop a script that, given a table of proxy addresses, can:
     • Identify all block heights associated with upgrades and implementation ABI changes.
     • Use the Etherscan API to retrieve the ABI data for each implementation associated with these block heights.

2. Dynamic Loading and Event Parsing:

   • Implement functionality to dynamically load the ABI data (in JSON format) at runtime.
   • Use this dynamically loaded ABI data to parse events on-the-fly while the sidecar is recovering.
   • Ensure that the sidecar can continue to listen for and process events seamlessly after catching up.

Acceptance Criteria

• [ ] A script that successfully identifies and retrieves ABI changes at specific block heights for given proxy addresses.
• [ ] Integration with the Etherscan API to fetch ABI data automatically.
• [ ] A mechanism to dynamically load ABI data at runtime.
• [ ] The system should be able to parse events using the loaded ABI data during the recovery process.
• [ ] Post-recovery, the sidecar should continue listening and processing events without interruption.

Additional Notes

• Handling should support multiple deployments and networks
• Ensure that the system handles cases where ABI data is unavailable or incomplete.
• Proper error handling and logging should be included to trace any issues during execution.

[ypatil12]

How do we handle the edge case of a contract ABI not being verified when we upgrade? Would we have to backfill?

[jac18281828]

How do we handle the edge case of a contract ABI not being verified when we upgrade? Would we have to backfill?

This will not be automatic. Upgrade will be manually confirmed. Verified ABI will be required for releases.