EOS EVM Node v1.0.0-rc2

Introduction

The latest release candidate introduces to a fix to issues discovered with how EOS EVM Node managed field extensions.

Read on for more details.

Updates

Improve block encode and decode logic to allow more flexibile field extensions

PRs

• (220) [1.0] Use updated silkworm with the new block-extra-data storage

It was discovered that within EOS EVM Node v1.0.0-rc1 that the logic would break if block_body.withdrawals exists but block_body.consensus_parameter_index did not exist.

    void encode(Bytes& to, const BlockBody& block_body) {
        encode_header(to, rlp_header_body(block_body));
        encode(to, block_body.transactions);
        encode(to, block_body.ommers);
        if (block_body.consensus_parameter_index) {
            encode(to, *block_body.consensus_parameter_index);
        }
        if (block_body.withdrawals) {
            encode(to, *block_body.withdrawals);
        }
    }

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 0.7.x or v1.0.0-rc1 version by replacing the binaries.

Further details on changes since last release

Contributors

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

• @elmato

Full list of changes since last release

PRs

• (220) [1.0] Use updated silkworm with the new block-extra-data storage
• (222) Bump 1.0.0-rc2 version

Full Changelog: v1.0.0-rc1...v1.0.0-rc2