Deployed bytecode error about pure-evm HOT 9 CLOSED

Awesome, thanks!

from pure-evm.

pure-evm can only execute evm bytecode that computes pure functions, so the code being executed should never read from or modify state.

Are you trying to read contract storage (considering it's a view function)?

from pure-evm.

No, the contract storage isn't being read or modified. It could be a pure function, but it would break the interface we are inheriting.

However, this problem persisted even when I used a pure function. Using ethers v5 and solidity 0.6.4 if that helps

from pure-evm.

Please attach a minimum reproducible example and I'll take a look.

from pure-evm.

Without looking at your code, it seems the problem is that the depth() externality is being called by your code (which would result in the given error, as expected).

I took a quick look at the parity-ethereum/open-ethereum codebase and it looks like it's only called on contract creation or cross contract calls.

So I would guess your bytecode has at least one of those opcodes in it, i.e.,instructions::CREATE | instructions::CREATE2, instructions::CALL | instructions::CALLCODE | instructions::DELEGATECALL | instructions::STATICCALL.

from pure-evm.

Sure, here is a simple reproduction. Just install, build, and test and you should see the same failure.

That's interesting. Was chatting with @HeikoFisch about it on our side, and we were thinking it might be due to the usage of sha256 or recover within the pure or view function

from pure-evm.

If I recall correctly, all Ethereum "builtin" functions like sha256 and recover execute as cross contract calls at builtin addresses, which would explain the error you're receiving.

from pure-evm.

Yeah, they would appear as contract calls in the compiled code.

So even though this is accepted as pure by the EVM it doesn't look like it will work within this library, bummer! Do you have any plans on supporting these precompile calls in the future?

from pure-evm.

There's currently no plans for feature development on this project, but I filed a new issue to track this feature request. See #7.

from pure-evm.