@ethereumjs/vm v5.0.0-beta.1
Pre-releaseATTENTION: This is a pre-release and only meant to be used for testing purposes.
Do not use in production!
Feedback is extremely welcome, please use the beta.1
Releases feedback issue #923 or our Discord channel.
New Package Name
Attention! This new version is part of a series of EthereumJS releases all moving to a new scoped package name format. In this case the library is renamed as follows:
ethereumjs-vm
->@ethereumjs/vm
Please update your library references accordingly or install with:
npm i @ethereumjs/vm
Support for all current Hardforks / HF API Changes
This is the first release of the VM which supports all hardforks currently applied on mainnet starting with the support of the Frontier HF rules all along up to MuirGlacier. 🎉
The following HFs have been added:
- Spurious Dragon, PR #791
- Tangerine Whistle, PR #807
- DAO, PR #843
- Homestead, PR #815
- Frontier, PR #828
A VM with the specific HF rules (on the chain provided) can be instantiated by passing in a Common
instance:
import VM from '@ethereumjs/vm'
import Common from '@ethereumjs/common'
const common = new Common({ chain: 'mainnet', hardfork: 'spuriousDragon' })
const vm = new VM({ common })
Breaking: The default HF from the VM has been updated from petersburg
to instanbul
. The HF setting is now automatically taken from the HF set for Common.DEAULT_HARDFORK
, see PR #906.
Breaking: Please note that the options to directly pass in chain
and hardfork
strings have been removed to simplify the API. Providing a Common
instance is now the only way to change the chain setup, see PR #863
Berlin HF Support / HF-independent EIPs
This releases adds support for subroutines (EIP-2315
) which gets activated under the berlin
HF setting which can now be used as a hardfork
instantiation option, see PR #754.
Attention! Berlin HF support is still considered experimental and implementations can change on non-major VM releases!
Support for BLS12-381 precompiles (EIP-2537
) is added as an independent EIP implementation - see PR #785 - since there is still an ongoing discussion on taking this EIP in for Berlin or using a more generalized approach on curve computation with the Ethereum EVM (evm384
by the eWASM team).
Another new EIP added is the EIP-2929
with gas cost increases for state access opcodes, see PR #889.
These integrations come along with an API addition to the VM to support the activation of specific EIPs, see PR #856, PR #869 and PR #872.
This API can be used as follows:
import VM from '@ethereumjs/vm'
const vm = new VM({ eips: [2537] })
API Change: New Major Library Versions
The following EthereumJS
libraries which are used within the VM internally and can be passed in on instantiation have been updated to new major versions.
merkle-patricia-tree
v3
(VM optionstate
) ->merkle-patricia-tree
v4
, PR #787ethereumjs-blockchain
v4
->@ethereumjs/blockchain
v5
, PR #833ethereumjs-common
v1
->@ethereumjs/common
v2
Breaking: If you pass in instances of these libraries to the VM please make sure to update these library versions as stated. Please also take a note on the package name changes!
All these libraries are now written in TypeScript
and use promises instead of callbacks for accessing their APIs.
New StateManager Interface / StateManager API Changes
There is now a new TypeScript
interface for the StateManager
, see PR #763. If you are using a custom StateManager
you can use this interface to get better assurance that you are using a StateManager
which conforms with the current StateManager
API and will run in the VM without problems.
The integration of this new interface is highly encouraged since this release also comes with StateManager
API changes. Usage of the old ethereumjs-account package (this package will be retired) has been replaced by the new Account class
from the ethereumjs-util
package. This affects all Account
related StateManager
methods, see PR #911.
The Util package also introduces a new Address class. This class replaces all current Buffer
inputs on StateManager
methods representing an address.
Dual ES5 and ES2017 Builds
We significantly updated our internal tool and CI setup along the work on PR #913 with an update to ESLint
from TSLint
for code linting and formatting and the introduction of a new build setup.
Packages now target ES2017
for Node.js builds (the main
entrypoint from package.json
) and introduce a separate ES5
build distributed along using the browser
directive as an entrypoint, see PR #921. This will result in performance benefits for Node.js consumers, see here for a releated discussion.
Other Changes
Changes and Refactoring
- Group opcodes based upon hardfork, PR #798
- Split opcodes logic into codes, fns, and utils files, PR #896
- Group precompiles based upon hardfork, PR #783
- Breaking: the
step
event now emits anethereumjs-util
Account object instead of an ethereumjs-account (package retired) object - Breaking:
NewContractEvent
now emits anaddress
of typeAddress
(seeethereumjs-util
) instead of aBuffer
, PR #919 - Breaking:
EVMResult
now returns acreatedAddress
of typeAddress
(seeethereumjs-util
) instead of aBuffer
, PR #919 - Breaking:
RunTxResult
now returns acreatedAddress
of typeAddress
(seeethereumjs-util
) instead of aBuffer
, PR #919 - Breaking:
RunCallOpts
now expectsorigin
,caller
andto
inputs to be of typeAddress
(seeethereumjs-util
) instead of aBuffer
, PR #919 - Breaking:
RunCodeOpts
now expectsorigin
,caller
and
address
inputs to be of typeAddress
(seeethereumjs-util
) instead of aBuffer
, PR #919 - Make
memory.ts
use Buffers instead of Arrays, PR #850 - Use
Map
forOpcodeList
andopcode
handlers, PR #852 - Compare buffers directly, PR #851
- Moved gas base fees from VM to Common, PR #806
- Return precompiles on
getPrecompile()
based on hardfork,
PR #783 - Removed
async
dependency, PR #779 - Updated
ethereumjs-util
to v7, PR #748
CI and Test Improvements
- New benchmarking tool for the VM, CI integration on GitHub actions, PR #794 and PR #830
- Various updates, fixes and refactoring work on the test runner, PR #752 and PR #849
- Integrated
ethereumjs-testing
code logic into VM for more flexible future test load optimizations, PR #808 - Transition VM tests to TypeScript, PR #881 and PR #882
Bug Fixes