- EELS is an execution layer reference implementation in Python.
- It is updated with mainnet.
- It fills assessments, and passes present ones.
- There’s an instance of an EIP applied in EELS beneath.
After greater than a yr in improvement, we’re happy to publicly introduce the Ethereum Execution Layer Specification (affectionately generally known as EELS.) EELS is a Python reference implementation of the core elements of an Ethereum execution consumer 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 mainnet1, 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 shoppers (which frequently combine a number of forks in the identical codepath.)
Starting in 2021, as a mission of ConsenSys’ Quilt workforce 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 particular conduct of an EVM instruction.
Drawing on the profitable Consensus Layer Specification, we got down to create an analogous executable specification for the execution layer.
At present, 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 numerous 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 invaluable complement to it:
Here is a video walk-through of adding a simple EVM instruction if that is your sort 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 Atmosphere: 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:
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 would like EELS to develop into the default method to specify Core EIPs, the primary place EIP authors go to prototype their proposals, and the absolute best reference for a way Ethereum works.