EOS EVM Node v1.0.0-rc3

Introduction

The latest release candidate introduces a fix to issues discovered with how non-legacy transactions where serialized into the database.

Read on for more details.

Updates

Change db serialization format for non-legacy transactions

PRs

• (232) [1.0] Update silkworm 1.0.1

The eos-evm-node previously stored RLP-serialized transactions in the database in a format that prevented directly obtaining the transaction hash by hashing the binary blob data. The current fix uses a transaction binary representation compatible with direct hashing, as other parts of the code assumed that representation.

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 version by replacing the binaries. If upgrading from v1.0.0-rc1 or v1.0.0-rc2 replay is needed.

Further details on changes since last release

Contributors

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

• @taokayan
• @elmato

Full list of changes since last release

PRs

• (221) [1.0->main] add integration test for differen test token
• (225) [1.0 -> main] Bump 1.0.0-rc1 version
• (226) [1.0 -> main] Use updated silkworm with the new block-extra-data storage
• (227) [1.0 -> main] Bump 1.0.0-rc2 version
• (231) [1.0] add get transaction & get transaction receipt from rpc test
• (232) [1.0] Update silkworm 1.0.1
• (233) [1.0] Bump 1.0.0-rc3 version

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