EIPs/eip-3540.md at 96cdc83e454379eb54aa0163cc7b6621cc646cad

mirror of https://github.com/status-im/EIPs.git synced 2025-02-24 04:38:29 +00:00

Alex Beregszaszi eae1779f0e

2021-07-29 10:21:58 +00:00

14 KiB

Raw Blame History

eip	title	author	discussions-to	status	type	category	created	requires
3540	EVM Object Format (EOF) v1	Alex Beregszaszi (@axic), Paweł Bylica (@chfast), Andrei Maiboroda (@gumb0)	https://ethereum-magicians.org/t/evm-object-format-eof/5727	Draft	Standards Track	Core	2021-03-16	3541

Abstract

We introduce an extensible and versioned container format for the EVM with a once-off validation at deploy time. The version described here brings the tangible benefit of code and data separation, and allows for easy introduction of a variety of changes in the future. This change relies on the reserved byte introduced by EIP-3541.

Motivation

On-chain deployed EVM bytecode contains no pre-defined structure today. Code is typically validated in clients to the extent of JUMPDEST analysis at runtime, every single time prior to execution. This poses not only an overhead, but also a challenge for introducing new or deprecating existing features.

Validating code during the contract creation process allows code versioning without an additional version field in the account. Versioning is a useful tool for introducing or deprecating features, especially for larger changes (such as significant changes to control flow, or features like account abstraction).

The format described in this EIP introduces a simple and extensible container with a minimal set of changes required to both clients and languages, and introduces validation.

The first tangible feature it provides is separation of code and data. This separation is especially beneficial for on-chain code validators (like those utilised by layer-2 scaling tools, such as Optimism), because they can distinguish code and data (this includes deployment code and constructor arguments too). Currently they a) require changes prior to contract deployment; b) implement a fragile method; or c) implement an expensive and restrictive jump analysis. Code and data separation can result in ease of use and significant gas savings for such use cases. Additionally, various (static) analysis tools can also benefit, though off-chain tools can already deal with existing code, so the impact is smaller.

A non-exhaustive list of proposed changes which could benefit from this format:

Including a JUMPDEST-table (to avoid analysis at execution time) or removing JUMPDESTs entirely.
Introducing static jumps (with relative addresses) and jump tables, and disallowing dynamic jumps at the same time.
Requiring code section(s) to be terminated by STOP. (Assumptions like this can provide significant speed improvements in interpreters, such as a speed up of ~7% seen in evmone.)
Multi-byte opcodes without any workarounds.
Representing functions as individual code sections instead of subroutines.
Introducing a specific section for the EIP-2938 Account Abstraction "top-level AA execution frame", simplifying the proposal.

Specification

We use RFC2119 keywords in this section.

In order to guarantee that every EOF-formatted contract in the state is valid, we need to prevent already deployed (and not validated) contracts from being recognized as such format. This is achieved by choosing a byte sequence for the magic that doesn't exist in any of the already deployed contracts.

Remarks

For purely reference purposes we call the 0xEF byte the FORMAT.

The initcode is the code executed in the context of the create transaction, CREATE, or CREATE2 instructions. The initcode returns code (via the RETURN instruction), which is inserted into the account. See section 7 ("Contract Creation") in the Yellow Paper for more information.

The opcode 0xEF is currently an undefined instruction, therefore: It pops no stack items and pushes no stack items, and it causes an exceptional abort when executed. This means initcode or already deployed code starting with this instruction will continue to abort execution.

Code validation

In this fork we introduce code validation for new contract creation. To achieve this, we define a format called EVM Object Format (EOF), containing a version indicator, and a ruleset of validity tied to a given version.

We define the EOF prefix as the concatenation of FORMAT and the magic.

At block.number == HF_BLOCK new contract creation is modified:

if initcode or code starts with the EOF prefix, it is considered to be EOF formatted and will undergo validation specified in the following sections,
else if code starts with 0xEF, creation continues to result in an exceptional abort (the rule introduced in EIP-3540),
otherwise code is considered legacy code and the following rules do not apply to it.

Container specification

The container starts with the header:

description	length	value
format	1-byte	0xEF
magic	2-byte	0xCA 0xFE	Subject to change, may be removed.
version	1-byte	0x01	means EOF1

This is followed by one or more section headers:

description	length
section_kind	1-byte	Encoded as a 8-bit unsigned number.
section_size	2-bytes	Encoded as a 16-bit unsigned big-endian number.

The section kinds are defined as follows:

section_kind	meaning
0	terminator
1	code
2	data

If the terminator is encountered, section size MUST NOT follow.

The section contents follow after the header, in the order and size they are defined, without any padding bytes.

To summarise, the bytecode has the following format:

format, magic, version, (section_kind, section_size)+, 0, <section contents>

Validation rules

A bytestream starting with the EOF prefix declares itself conforming to the rules according to its version.

The rules of version=1 are specified below:

section_size MUST NOT be 0.
Exactly one code section MUST be present.
The code section MUST be the first section.
A single data section MAY follow the code section.
Stray bytes outside of sections MUST NOT be present. This includes trailing bytes after the last section.

Any other version is invalid.

(Note: Contract creation code SHOULD set the section size of the data section so that the constructor arguments fit it.)

Changes to execution semantics

For clarity, the container refers to the complete account code, while code refers to the contents of the code section only.

Jumpdest analysis is only run on the code.
Execution starts at the first byte of the code, and PC is set to this position within the container format (e.g. PC=10 for a container with a code and data section).
If PC goes outside of the code section bounds, execution aborts with failure.
PC returns the current position within the container.
JUMP/JUMPI uses an absolute offset within the container.
CODECOPY/CODESIZE/EXTCODECOPY/EXTCODESIZE/EXTCODEHASH keeps operating on the entire container.
The input to CREATE/CREATE2 is still the entire container.

Changes to contract creation semantics

For clarity, the EOF prefix together with a version number n is denoted as the EOFn prefix, e.g. EOF1 prefix.

If initcode's container has EOF1 prefix it must be valid EOF1 code.
If code's container has EOF1 prefix it must be valid EOF1 code.

Rationale

EVM and/or account versioning has been discussed numerous times over the past years. This proposal aims to learn from them. See this collection of previous proposals for a good starting point.

Execution vs. creation time validation

This specification introduces creation time validation, which means:

All created contracts with EOFn prefix are valid according to version n rules. This is very strong and useful property. The client can trust that the deployed code is well-formed.
In future, this allows to serialize JUMPDEST map in the EOF container and eliminate the need of implicit JUMPDEST analysis required before execution.
Or to completely remove the need for JUMPDEST instructions.
This helps with deprecating EVM instructions and/or features.
The biggest disadvantage is that deploy-time validation of EOF code must be enabled in two hard-forks. However, the first step (EIP-3541) is already deployed in London.

The alternative is to have execution time validation for EOF. This is performed every single time a contract is executed, however clients may be able to cache validation results. This alternative approach has the following properties:

Because the validation is consensus-level execution step, it means the execution always requires the entire code. This makes code merkleization impractical.
Can be enabled via a single hard-fork.
Better backwards compatibility: data contracts starting with the 0xEF byte or the EOF prefix can be deployed. This is a dubious benefit however.

Contract creation restrictions

The Changes to contact creation semantics section defines minimal set of restrictions related to the contract creation: if initcode or code has the EOF1 container prefix it must be validated. This adds two validation steps in the contract creation, any of it failing will result in contract creation failure.

Since initcode and code are evaluated for EOF1 independently, number of interesting combinations are allowed:

Create transaction with EOF1 initcode can deploy legacy contract,
EOF1 contract can execute CREATE instruction with legacy initcode to create new legacy contract,
Legacy contract can execute CREATE instruction with EOF1 initcode to create new EOF1 contract,
Legacy contract can execute CREATE instruction with EOF1 initcode to create new legacy contract,
etc.

To limit the number of exotic bytecode version combinations, additional restrictions are considered, but currently are not part of the specification:

The EOF version of initcode must much the version of code.
An EOF1 contract must not create legacy contracts.

Finally, create transaction must be allowed to contain legacy initcode and deploy legacy code because otherwise there is no transition period allowing upgrading transaction signing tools. Deprecating such transactions may be considered in future.

The FORMAT byte

The 0xEF byte was chosen because it is reserved for this purpose by EIP-3541.

Section structure

We have considered different questions for the sections:

Streaming headers (i.e. section_header, section_data, section_header, section_data, ...) are used in some other formats (such as WebAssembly). They are handy for formats which are subject to editing (adding/removing sections). That is not a useful feature for EVM. One minor benefit applicable to our case is that they do not require a specific "header terminator". On the other hand they seem to play worse with code chunking / merkleization, as it is better to have all section headers in a single chunk.
Whether to have a header terminator or to encode number_of_sections or total_size_of_headers. Both raise the question how large of a value these fields should be able to hold. While today there will be only two sections, in case each "EVM function" would become a separate code section, a fixed 8-bit field may not be big enough. A terminator byte seems to avoid these problems.
Whether to encode section_size as a fixed 16-bit value or some kind of variable length field (e.g. LEB128). We have opted for fixed size, because it simplifies client implementations, and 16-bit seems enough, because of the currently exposed code size limit of 24576 bytes (see EIP-170 and EIP-2677). Should this be limiting in the future, a new EOF version could change the format.

Backwards Compatibility

This is a breaking change given that any code starting with 0xEF was not deployable before (and resulted in exceptional abort if executed), but now some subset of such codes can be deployed and executed successfully.

The choice of magic guarantees that none of the contracts existing on the chain are affected by the new rules.

Test Cases

Reference Implementation

evmone: https://github.com/ethereum/evmone/pull/303
Solidity: https://github.com/ethereum/solidity/tree/eof1

Simplified implementations

Given the rigid rules of EOF1 it is possible to implement support for the container in clients using very simple pattern matching (the following assumes magic = 0x00):

If code starts with 0xEF 0x00 0x01 codelen1 codelen2 0x02 datalen1 datalen2 0x00, then calculate total_size = (9 + (codelen1 << 8 | codelen2) + (datalen1 << 8 | datalen2)). If total_size == container_size then it is a valid EOF1 code with a code and data section.
If code starts with 0xEF 0x00 0x01 codelen1 codelen2 0x00, then calculate total_size = 7 + (codelen1 << 8 | codelen2). If total_size == container_size then it is a valid EOF1 code with a code section only.
Otherwise if it starts with 0xEF, it is invalid.
Otherwise if it does not start with 0xEF, it is valid legacy code.

However, future versions may introduce more sections or loosen up restrictions, requiring clients to actually parse sections instead of pattern matching.

Security Considerations

TBA

14 KiB Raw Blame History