Add EIP: EOF - Data section access instructions

[gumb0]

No description provided.

[eth-bot]

✅ All reviewers have approved.

[github-actions]

The commit 2352fbc (as a parent of f2685f3) contains errors.
Please inspect the Run Summary for details.

[g11tech]

i think it would be better to specify activation independently (and this EIP already specifies that it depends on 3540). Their activation is dependent on inclusion of the EIP in a particular hardfork which would be an independent decision by the ACD.

Suggested change

	We introduce four new instructions on the same block number [EIP-3540](./eip-3540.md) is activated on:
	We introduce four new instructions:

[axic]

Most of EOF must be activated at the same time, otherwise the functionality is very limited.

[lightclient]

LGTM

[eth-bot]

All Reviewers Have Approved; Performing Automatic Merge...

[ProphetZX]

Just a short question: Why do you plan to implement a DATALOAD and DATALOADN method/function? Is it as a backup version, so if either gets rejected in a specific situation, you‘d want to switch to the other one?

[ProphetZX]

Just have some doubts it‘s really necessary. :)

[gumb0]

Just a short question: Why do you plan to implement a DATALOAD and DATALOADN method/function? Is it as a backup version, so if either gets rejected in a specific situation, you‘d want to switch to the other one?

It's in Motivation:

DATALOADN is an optimized version of DATALOAD, where data offset to read is set at compilation time, and therefore need not be validated at run-time, which makes the instruction cheaper.

DATALOADN can be used when the offset is known at compile-time, DATALOAD is needed to read from offset determined at run-time.