Proposal to add EIP-3540 to Shanghai

[axic]

This is an early indication to seek inclusion of EIP-3540 (EVM Object Format) into Shanghai.

We appreciate that the EIP text may be simplified to only keep "hard fork 2", because "hard fork 1" is now covered by EIP-3541. It also depends on a value to be determined after London (via EIP-3541), however we think the core design is not expected to change significantly.

There is an implementation in geth and solidity, and a partial implementation in evmone.

[axic]

An explainer (with roadmap) was published here: https://notes.ethereum.org/@ipsilon/evm-object-format-overview

It explains the reason for the two hard forks and potential future features after Shanghai.

[timbeiko]

@axic do you want to give an overview of 3540 on the next ACD? I don't think we'll be discussing Shanghai inclusion, but it may be good to remind people of the EIP, answer questions, etc. if time permits.

[axic]

@timbeiko probably we can give a brief update/reminder, but for the next ACD we should have the EIP cleared from the two forks, so it may be a better time then.

[axic]

@timbeiko you wanted this on the agenda, will we have it today or next time?

[axic]

@timbeiko as a heads up, apart from #360 we have another addition for EOF we want to propose, but couldn't finish the EIP this week. We hope these three could be launched at the same time, but at least EIP-3540+EIP-3670 would be nice. However they are independent by design, so even just having EIP-3540 first is sufficient.

[timbeiko]

On ACD131 we decided to move this EIP to CFI for Shanghai. Closing this issue for now. We can reopen if, for whatever reasons, issues arise about the EIP's inclusion in the upgrade.