EIP-4788: Beacon root in EVM

By including the ommersHash validation, clients can use existing code with only minimal changes (supplying the actual state root) during block production and verification.

Having the beacon state root value in the ommers field means that it is fairly straightforward to provide the value from the block data to the EVM execution context for client implementations as they stand today.

I would like to get validation from execution client teams that this is actually of meaningful value. It may be just as easy to completely remove the uncle validation code entirely as it would be to pseudo-replace it with this. If so, then I would strongly advocate for changing this into a single 32-byte hash rather than an array of 1 item.

2 Likes