Add Ethereum Smart Contract binary bytecode matching

[Alexvozhak]

Description:

This PR enhances diffyscan by integrating Ethereum smart contract binary matching. It incorporates functionalities from verify-bytecode.ts and bytecode_verificator.sh.

---

Key Changes:

• Showcases:

  • Sepolia Network: Added support for all contracts by extending lido_dao_sepolia_config.json.
  • Holesky Network: Added support for 3 out of 53 contracts by extending lido_dao_holesky_config.json.

• New Modules and Refactoring:

  • Binary Comparison Logic: Introduced binary_verifier.py to handle binary comparison of contracts.
  • Argument Encoding: Added encoder.py for encoding contract arguments, referencing the Solidity ABI specification.
  • Compiler Module: Moved all source compilation code to compiler.py.
  • Calldata Handling: Created calldata.py for calculating and parsing constructor arguments from configurations.
  • Type Definitions: Renamed and extended types.py to custom_types.py.
  • Node Interactions:
    • Encapsulated interactions with the local Hardhat node in hardhat.py.
    • Moved common node operations to node_handler.py.
  • Exception Handling: Added specific exceptions for new features in custom_exceptions.py.

• Configurations and Documentation:

  • Configuration Updates:
    • Extended lido_dao_sepolia_config.json and lido_dao_holesky_config.json with a binary_comparison section.
    • Added specific Hardhat configurations for Sepolia and Holesky networks.
  • Documentation:
    • Updated the README to reflect new features and usage instructions.
    • Included support for user-defined Hardhat configurations as shown in the README example.

• Improvements and Fixes:

  • Code Quality:
    • Fixed existing errors identified by the mypy linter.
    • Enhanced code readability and organization.
  • Backwards compatibility: Ensured that existing diffyscan usage remains unaffected.

---

Implemented Logic for Contract Code Matching:

1. Source Retrieval: Obtain contract sources from Etherscan.
2. Source Diffing: Perform source code diffing as previously implemented.
3. Bytecode Matching: Compile the contracts and attempt to match the bytecode obtained from the RPC node.
4. Matching Outcome:
   • Success: If the bytecode matches, proceed to the next contract.
   • Metadata Differences: If only the metadata differs, display a warning but continue processing.
5. Error Handling:
   • No Immutables: If there are no immutables and the bytecode doesn't match, display an error.
   • With Immutables: If immutables are present and the configuration includes constructor calldata or parameters, attempt to deploy the contract and compare the resulting bytecode.

---

By integrating these enhancements, diffyscan has been enriched with the ability to verify smart contracts at the bytecode level, ensuring greater reliability and security in contract deployment and verification processes.

[TheDZhon]

👀

[TheDZhon]

👀

[TheDZhon]

Seems the PR is ready to merge 🌟 except only for two things:

1. An outstanding branch conflict it has
2. Metadata parsed as opcodes while it shouldn't, see https://docs.soliditylang.org/en/latest/metadata.html#encoding-of-the-metadata-hash-in-the-bytecode

see as a reference:

https://playground.sourcify.dev/
address: 0x76A50b8c7349cCDDb7578c6627e79b5d99D24138
network: #10 OP Mainnet

[TheDZhon]

https://github.com/lidofinance/aave-delivery-infrastructure/blob/main/verifications/scripts/verify-bytecode.ts#L479-L494
here is the example of the metadata parsing btw

[TheDZhon]

LGTM, accepting to upstream 🍏