Ethereum Execution Layer Specification | Ethereum Foundation Blog

tl;dr

• EELS is an execution layer reference implementation in Python.
• It is updated with mainnet.
• It fills assessments, and passes current ones.
• There’s an instance of an EIP carried out in EELS under.

Introduction

After greater than a 12 months in improvement, we’re happy to publicly introduce the Ethereum Execution Layer Specification (affectionately referred to as EELS.) EELS is a Python reference implementation of the core parts of an Ethereum execution shopper centered on readability and readability. Supposed as a non secular successor to the Yellow Paper that is extra programmer pleasant and up-to-date with post-merge forks, EELS can fill and execute state assessments, observe mainnet¹, and is a superb place to prototype new EIPs.

EELS supplies full snapshots of the protocol at every fork—together with upcoming ones—making it a lot simpler to observe than EIPs (which solely suggest modifications) and manufacturing purchasers (which regularly combine a number of forks in the identical codepath.)

Historical past

Starting in 2021, as a challenge of ConsenSys’ Quilt group and the Ethereum Basis, the eth1.0-spec (because it was identified then) was impressed by the sheer frustration of getting to decipher the cryptic notation of the Yellow Paper (Figure 1) to know the precise habits of an EVM instruction.

Drawing on the profitable Consensus Layer Specification, we got down to create the same executable specification for the execution layer.

Current

Right now, EELS is consumable as a traditional Python repository and as rendered documentation. It is nonetheless a bit tough across the edges, and would not present a lot in the best way of annotations or English explanations for what varied items do, however these will include time.

It is simply Python

Hopefully a side-by-side comparability of the Yellow Paper and the equal code from EELS can present why EELS is a worthwhile complement to it:

def less_than(evm: Evm) -> None:
    # STACK
    left = pop(evm.stack)
    proper = pop(evm.stack)

    # GAS
    charge_gas(evm, GAS_VERY_LOW)

    # OPERATION
    outcome = U256(left < proper)

    push(evm.stack, outcome)

    # PROGRAM COUNTER
    evm.computer += 1

Whereas Figure 2 may be digestible to teachers, Figure 3 is indisputably extra pure to programmers.

Here is a video walk-through of adding a simple EVM instruction if that is your form of factor.

Writing Exams

It bears repeating: EELS is simply common Python. It may be examined like some other Python library! Along with the whole ethereum/tests suite, we even have a number of pytest assessments.

With somewhat assist from execution-spec-tests, any assessments written for EELS will also be utilized to manufacturing purchasers!²

Exhibiting Variations

Having snapshots at every fork is nice for a sensible contract developer popping in to see the specifics of how an EVM instruction works, however is not very useful for shopper builders themselves. For them, EELS can show the variations between forks:

An Instance EIP

EIP-6780 is the primary EIP to get an EELS implementation offered by the creator, Guillaume Ballet! Let’s have a look.

First, we introduce a created_contracts variable to the EVM with transaction-level scope:

 @dataclass
 class Setting:
     caller: Deal with
     block_hashes: Checklist[Hash32]
     origin: Deal with
     coinbase: Deal with
     quantity: Uint
     base_fee_per_gas: Uint
     gas_limit: Uint
     gas_price: Uint
     time: U256
     prev_randao: Bytes32
     state: State
     chain_id: U64
+    created_contracts: Set[Address]

Second, we word which contracts have been created in every transaction:

+    evm.env.created_contracts.add(contract_address)

Lastly, we modify selfdestruct so it solely works for contracts famous in created_contracts:

-    # register account for deletion
-    evm.accounts_to_delete.add(originator)
-
+    # Solely proceed if the contract has been created in the identical tx
+    if originator in evm.env.created_contracts:
+
+        # register account for deletion
+        evm.accounts_to_delete.add(originator)
+

Future

We would like EELS to change into the default approach to specify Core EIPs, the primary place EIP authors go to prototype their proposals, and the absolute best reference for a way Ethereum works.

Should you’re concerned about contributing or prototyping your EIP, be part of us on the #specifications channel or seize a problem from our repository.