Does Besu spawn a `MessageFrame` for CALLs to precompiles ?
Closed this issue · 2 comments
OlivierBBB commented
In simple tests we see that Besu creates a MessageFrame for EOA calls but apparently not for precompile calls. Is that indeed the case and if so how to discover the returnGas i.e. the gas that is returned by the precompile to its caller ?
lu-pinto commented
Are you sure about that? I don't see any distinction between precompiles and others while executing CALL, see my answer here.
Regarding the returnGas - do you mean the gas you pay on input data? I don't see any gas being taken while running the precompile code. Assuming that's the one, it only gets handed back in privacy based precompiled contracts from what I can see: MessageCallProcessor.java#L161-L163
letypequividelespoubelles commented
answer is yes