You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Display all functionSelectors/perfectMatches (in case several exist)
Ethereum mainnet (from drop-down doesn't work currently; API key missing)
Handle edge cases better: Uint256/Bytes32 can not be distinguished well from looking at the bytecode; evMole prefers to display them as uint256, while looking at the database of openChain.xyz can reveal that bytes32 is a better bet in terms of occurrence in some cases (e.g. function selector: 0x9b0b0fda in contract 0x5f5a404A5edabcDD80DB05E8e54A78c9EBF000C2; e.g. function selectors in contract 0x6D19E24564A13BC07C63976B84c212541da2E8Ac)
The front-end freezes when decoding some contracts -> find a better default gasLimit for the decoding -> timeout the request to fetch data from function selector database
Front-end cannot automatically detect poxy-implementation relationships in the bytecode -> check out if whatsABI should be used to detect this relationship -> display the proxy/beacon-proxy ABI + implementation ABI
uint256
, while looking at the database of openChain.xyz can reveal thatbytes32
is a better bet in terms of occurrence in some cases (e.g. function selector: 0x9b0b0fda in contract 0x5f5a404A5edabcDD80DB05E8e54A78c9EBF000C2; e.g. function selectors in contract 0x6D19E24564A13BC07C63976B84c212541da2E8Ac)gasLimit
for the decoding -> timeout the request to fetch data from function selector databasewhatsABI
should be used to detect this relationship -> display the proxy/beacon-proxy ABI + implementation ABINext Milestones:
Discussion/Feature request on
BlockScout
repo:Display ABI for unverified Solidity contracts using whatsabi tool and Ethereum signatures DB blockscout/blockscout#6203
Talk to
EtherScan
people -> Experimental integration intoEtherScan
.Discussion/Feature request on
REMIX IDE
repo:Talk to
Routescan
team.Talk to
Sourcify
team.The text was updated successfully, but these errors were encountered: