Andrey Petrov

Ah I think you're right, this is a bug. If `followProxies: false`, then the DiamondProxy resolving should be bundled into the `result.followProxies()` callback. I'll try that fix, but there might...

This was undone in https://github.com/shazow/whatsabi/commit/fe8fa90b53b7ea789c6a85e59e6a29e145622cdb since we weren't sure what behaviour we want yet. Also might be a good excuse to refactor autoload into more modular pieces to avoid recursing...

Looks like the constant we're looking for is stored at the end and loaded via `CODECOPY`, and whatsabi is failing to detect the end of the program so it's treating...

Good call, that's a bug! I believe the intention was to always include the selector, but need to double check whether there's some newer callpaths where this is not practical...

> If I can make a request, when the tool is unable to determine inputs, even just capping the calldata length can be very useful, as I'm using this for...

Hiya, what's an abstract chain contract? `0x85Ca16Fd0e81659e0b8Be337294149E722528731` doesn't have any code deployed, it's just an EOA right? https://etherscan.io/address/0x85Ca16Fd0e81659e0b8Be337294149E722528731

Ah interesting, haven't heard of Abstract Chain! It is getting the bytecode but it's not being parsed as EVM correctly. Is there something special about the way Abstract Chain works?...

For my notes, I'm testing it this way: ```console $ ETH_RPC_URL="https://api.mainnet.abs.xyz" ./examples/autoload.ts 0x85Ca16Fd0e81659e0b8Be337294149E722528731 $ ETH_RPC_URL="https://api.mainnet.abs.xyz" ./examples/bytecode.ts 0x85Ca16Fd0e81659e0b8Be337294149E722528731 ```