Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assigning version numbers to EVM changes #178

Open
axic opened this issue Nov 15, 2016 · 1 comment

Comments

Projects
None yet
4 participants
@axic
Copy link
Member

commented Nov 15, 2016

Motivation

To have consistent and simple way referring to EVM versions in clients and tools.

Specification

A limited subset of semantic versioning (semver) is introduced for EVM versions. Only a major and minor version numbers are used, patch level is omitted.

In the past, almost each hard fork made a breaking change (and thus introduced a new major bump) to the underlying EVM implementation, but this is not necessarily a requirement for future hard forks.

The past changes are versioned as follows:

  • 1.0 - Frontier
  • 1.1 - Homestead (+ EIP7)
  • 2.0 - EIP150.1c ("all but one", OOG changes)

EVM version identifier

The #154 proposal can be extended to include the above version numbers in a binary format. A straightforward way is to store major and minor as an 8 bit value each. Setting certain restrictions would allow to pack them into a single 8 bit value.

@chfast

This comment has been minimized.

Copy link
Contributor

commented Mar 11, 2019

Can wasm-like prefix be used. I.e. 4 bytes "\x00evm" + 4 bytes little endian version number?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.