The current bytecode analysing script requires manual editing. Users must manually calculate and input function selector hashes. The script can only process one address at a time.
Parametrize the searched values: Currently, you have to edit the Python script to search for something else. We propose making this more flexible.
Accept function signatures instead of function selector hashes: The current solution requires users to calculate the hash on their own before using it. We suggest allowing function signatures as input.
Accept a file with multiple addresses as input: Instead of one address, the script could process a file with multiple addresses. What should be the format of this file? Can you generate a simple file with addresses separated by \n characters, or could we get access to create this file ourselves?
Enable cascade runs: Allow the script to run multiple times to determine the likelihood that a Smart Contract makes a call to a precompile indirectly through another Smart Contract.
Problem
The current bytecode analysing script requires manual editing. Users must manually calculate and input function selector hashes. The script can only process one address at a time.
Solution
Current proposals of improving the bytecode analysing script are as follows:
Alternatives
No response