EOS EVM Node v1.0.4

Introduction

The latest patch release of EOS EVM Node introduces fixes for edge cases where state history connections may enter a stuck state and where call_eth would return insufficient gas values.

Read on for more details.

Updates

Improper use of state history's get_blocks_ack_request_v0 leading to "stuck" state history connection

PRs

• (328)[1.0] Remove blocks ack request from ship client

EOS EVM Node was incorrectly using the get_blocks_ack_request_v0 interface, which could lead to the state history connection entering a stuck state. send_get_blocks_ack_request has been removed to fix this issue.

call_eth returns insufficient gas when called with from field

PRs

• (330)[1.0] Update silkworm version to 1.0.8

When called with the from field, call_eth was returning insufficient gas values due to max_fee_per_gas, which had be previously added to resolve a prior assertion error. Because this issue was previously fixed, this part has been removed.

Building, compatibility, and upgrading

Building

The README in the eos-evm-node repository contains instructions on how to build EOS EVM Node and EOS EVM RPC.

Compatibility and upgrading

EOS EVM Node and EOS EVM RPC can be upgraded from the prior 1.0.x version by replacing the binaries.

Further details on changes since last release

Contributors

Special thanks to the contributors that submitted patches for this release:

• @taokayan
• @elmato
• @yarkinwho

Full list of changes since last release

PRs

• (321)[1.0] integration test for evmtx order
• (327)[1.0] Add eth_getLogs integration test
• (330)[1.0] Update silkworm version to 1.0.8
• (328)[1.0] Remove blocks ack request from ship client
• (338)[1.0] Bump 1.0.4 version

Full Changelog: v1.0.3...v1.0.4