- EELS is an execution layer reference implementation in Python.
- It is updated with mainnet.
- It fills checks, and passes current ones.
- There’s an instance of an EIP carried out in EELS beneath.
After greater than a yr in growth, 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 elements of an Ethereum execution consumer targeted 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 checks, comply with mainnet1, and is a superb place to prototype new EIPs.
EELS gives full snapshots of the protocol at every fork—together with upcoming ones—making it a lot simpler to comply with than EIPs (which solely suggest modifications) and manufacturing purchasers (which regularly combine a number of forks in the identical codepath.)
Starting in 2021, as a challenge of ConsenSys’ Quilt workforce and the Ethereum Basis, the eth1.0-spec (because it was recognized then) was impressed by the sheer frustration of getting to decipher the cryptic notation of the Yellow Paper (Figure 1) to grasp the particular habits of an EVM instruction.
Drawing on the profitable Consensus Layer Specification, we got down to create an identical executable specification for the execution layer.
Right this moment, EELS is consumable as a traditional Python repository and as rendered documentation. It is nonetheless a bit tough across the edges, and does not present a lot in the way in which 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:
This is a video walk-through of adding a simple EVM instruction if that is your form of factor.
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 consumer builders themselves. For them, EELS can show the variations between forks:
An Instance EIP
First, we introduce a created_contracts variable to the EVM with transaction-level scope:
@dataclass class Surroundings: caller: Handle block_hashes: Record[Hash32] origin: Handle coinbase: Handle 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 had been created in every transaction:
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) +
We wish EELS to change into the default option to specify Core EIPs, the primary place EIP authors go to prototype their proposals, and the absolute best reference for a way Ethereum works.