-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vmConfig.EWASMInterpreter is not passed to NewEVM #1
Comments
have you tried accessing |
@gballet The The commit ethereum@0e9dad2 of ethereum#17955 should fix the problem. But it is still a workaround rather for a complete solution. |
@chfast Once again, we agreed with @axic @karalabe and @holiman that fork rules were the way to go and your fix would activate WASM on pre-fork blocks, which must be prevented. Just setting |
Merged ethereum#17955 @cdetrio please check if you still see this issue. |
it was fixed, thanks! |
To run geth + EVMC/Hera, geth accepts the path to the Hera .so file in a
--vm.ewasm
flag. This path to Hera is then passed in vmConfig when callingnewBlockchain
here:go-ethereum/eth/backend.go
Lines 155 to 160 in 52dce7d
The problem is that another place where vmConfig is passed is from the rpc method
eth_estimateGas
, originating here: https://github.com/ewasm/go-ethereum/blob/tantalus-evmc6/internal/ethapi/api.go#L714. Here the vmConfig is empty, and it makes its way toNewEVM()
here: https://github.com/ewasm/go-ethereum/blob/tantalus-evmc6/core/vm/evm.go#L135As a temporary fix, in
NewEVM()
we're reading the Hera.so path from the env varEVMC_PATH
, with this patch: bb778d6. But we'd like to read it from the--vm.ewasm
flag instead.The text was updated successfully, but these errors were encountered: