Add EVMole integration for unverified contracts

[cdump]

Currently, abi.ninja is trying to use heimdall-rs for ABI extraction from unverified contracts.

I propose to add (or replace) it with EVMole, which has the following advantages:

• Better accuracy in function selectors extraction
• Significant improvement in accuracy for function arguments extraction
• Faster performance
• A JavaScript implementation with zero dependencies, allowing it to be embedded in abi.ninja without an external backend

It already has an online demo. You can see an example usage in the source code of that page (right inside the <script> tag).

My proposed logic for unverified contracts:

1. Load runtimeBytecode (requires an external RPC call to eth_getCode; 1rpc is used in the EVMole demo)
2. Get function selectors with the evmole.functionSelectors JS function (offline)
3. Resolve function selectors using an API, like https://openchain.xyz/signatures
4. For unresolved selectors from the previous step, extract arguments using evmole.functionArguments (offline)

What do you think about this?

[cdump]

@technophile-04 @portdeveloper what do you think about this?

[portdeveloper]

Hey I think it looks great but how many chains does EVMole support right now?

[cdump]

All EVM chains, because evmole doesn't interact with the chain, only the evm bytecode required

…

On Thu, Dec 19, 2024, 11:22 port ***@***.***> wrote: Hey I think it looks great but how many chains does EVMole support right now? — Reply to this email directly, view it on GitHub <#102 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADNWXYBIFZTRBTG6WG2OLT2GKM7JAVCNFSM6AAAAABI4DBS7OVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNRRGU2TQNY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[portdeveloper]

That definitely sounds interesting!