Process of rolling out EIP615 Static Jumps and other EVM opcode additions

Changes and improvements to the EVM can be made without a "hard fork". The question becomes how to coordinate and communicate to the rest of the toolchain – primarily languages / compilers that target the EVM – about these new opcodes, and then communicating to the wider community of smart contract developers that these new features can now be reliably used.

We think the process is as follows:

  • Implementation that people can look at
    • Aleth example is done
    • Parity, Geth, Trinity, Pantheon as other current clients to target
  • EIP moved to Last Call, then Final
  • Once accepted, becomes part of the official standard
  • PR against Yellow Paper / Jello Paper

Clients are free to deploy upgraded EVMs that contain new opcodes whenever they like.

Coordinate changes to languages / compilers (Solidity, Vyper, etc.)
* Vyper has already said they are interested

Once there is high coverage (99%?) of clients running an upgraded EVM (how to test for this? today, just version number), communicate that these opcodes can be used.

Other considerations:

  • testnet that gets to 99% coverage for earlier usage
tags: evm evolution eip615 ethereum
Select a repo