Releases: VaultaFoundation/evm-node
EOS EVM Node v0.6.0-rc2
Changes
Handle string id fields within requests
The previous version of EOS EVM RPC would fail to accept requests that had a string value for the id field. This release now accepts string values for the id field.
Fixed bug in eth_getLogs
A bug existed in the previous version of EOS EVM RPC in which some eth_getLogs requests could fail with an error message "failed alloc while reading". That bug has now been fixed.
Trace executor now generates trace for calls to pre-compiled contract addresses
In the previous version, a transfer or call to an address of a pre-compiled contract would erroneously not generate a trace. Traces are now generated for calls to pre-compiled contract addresses.
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.6.0-rc1 version by replacing the binaries. It is recommended to replay to ensure there are no missing traces.
Further details on changes since last release
Contributors
Special thanks to the contributors that submitted patches for this release:
Full list of changes since last release
PRs
Full Changelog: v0.6.0-rc1...v0.6.0-rc2
Contributors
Assets 2
EOS EVM Node v0.6.0-rc1
EOS EVM Node brings the components EOS EVM Node and EOS EVM RPC from the eos-evm repository into its own repository: eos-evm-node. In addition, the 0.6.0 release of EOS EVM Node introduces improvements over prior versions.
New features
Recent changes from upstream silkworm
More recent improvements from the upstream silkworm repository were brought into the ENF fork of silkworm which is a critical component of EOS EVM Node.
That automatically gives EOS EVM Node some enhancements such as batch request support.
Batch requests support
Users can now submit multiple actions or transactions to the EVM as a single request. This enhances efficiency, reduces transaction costs, and provides a better user experience for interacting with smart contracts and dApps.
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.5.2 version by replacing the binaries and relaunching with a replay.
Further details on changes since last release
Contributors
Special thanks to the contributors that submitted patches for this release:
Full list of changes since last release
This is the first release from the new repository, so a GitHub link to compare all changes since the 0.5.2 release cannot be provided. But the list of all PRs merged in the new repository is provided below.
PRs
- (1) Many fixes
- (4) Merge elmato/dev
- (7) Update silkworm
- (8) Use regular endpoints as the default values in command line options
- (10) Fix compilation
- (16) Get EOS EVM Node Build job to succeed
- (17) eos-evm-node repo integration test
- (18) Update supported Ubuntu and gcc versions in README
- (3) Refactor to allow reconnection to SHiP endpoints after connection lost.
- (21) Replace tx_wrapper with eos-evm-miner for integration test.
- (27) fix special signature handling
- (32) Correct processing of pushtx actions in ship_receiver_plugin
- (42) Add conan install to build instructions
- (41) Fix nodeos_eos_evm_server.py
- (43) Fix eos-evm-rpc crash
- (44) Bump 0.6.0-rc1 version
