Update EIP-2935: Update EVM bytecode to add the system set update op

[g11tech]

TODO

• update deployment tx
• mine and update new address
  • deployment details are as calculated and tested in ethereumjs test code
    • util,vm,evm: update the 2935 latest bytecode in test and fix address conversion issues  ethereumjs/ethereumjs-monorepo#3447

[eth-bot]

✅ All reviewers have approved.

[gballet]

there is no function dispatcher, which I understand is a solidity-level concept, but that means that a code written in solidity will either have to a) use a low-level call function written in yul, or b) this contract will have to ignore the first 4 bytes of the calldata, just in case they are added by a solidity call.

Also, this effectively says that unless you're the system contract, you're going a get. I would rather do it the right way, but I would check with matt how the 4788 contract does it.

[g11tech]

Also, this effectively says that unless you're the system contract, you're going a get. I would rather do it the right way, but I would check with matt how the 4788 contract does it.

this is exactly how 4788 does it

[gballet]

i added a comment about not sanitizing the input of set but apart from that, I think this is good to merge.

[gballet]

Suggested change

	Similar to [EIP-4788](./eip-4788.md) above contract provides a `set` mechanism which clients can choose to update the block's parent hash in the ring buffer instead of direct state update. For this clients should call this contract with `SYSTEM_ADDRESS` as caller and provide `32` bytes parent block hash as input.
	Similar to [EIP-4788](./eip-4788.md) above contract provides a `set` mechanism which clients can choose to update the block's parent hash in the ring buffer instead of direct state update. For this clients should call this contract with `SYSTEM_ADDRESS` as caller and provide `32` bytes parent block hash as input.
	Note that the inputs to the `set` method are not sanitized and it is the caller's responsibility to ensure that the ring buffer isn't overrun. This choice was made to support a change in the ring buffer size without having to redeploy a new contract.

[g11tech]

we will also need to change the get method as well. but there is another consideration:

the contracts that would directly call the contract would break if we modify ring buffer length and expcted them to mod the input in a new way

[eth-bot]

All Reviewers Have Approved; Performing Automatic Merge...