Upgrade EVM to Cancun

[khoau2u]

• Prerequisites: no, standalone, may consider 4d30fee if bundle with Implement paymaster flow (closes #94) #95 is preferred
• References: This PR refer to issue number no Upgrade EVM to Cancun #96
• Description:
• Define Cancun hard fork feature activators
• Merge and fix EVM opcodes, instructions, features, etcetera from ethereum upstream

Please check if what you want to add to go-u2u list meets Contribution guidelines, maintainers note and Quality standard.

[khoau2u]

I see that we have difficulty to validate this PR. Here are what is exactly included in this PR:

• EIP-1153 Transient storage opcodes
• EIP-3855 PUSH0
• EIP-3860 Limit and meter initcode
• EIP-4844 Blob transaction, precompiles and default trusted setup
• EIP-5656 MCOPY
• EIP-6780 SELFDESTRUCT only in same transaction
• EIP-7516 BLOBBASEFEE
• INVALID, RANDAO (zeroed) opcode
• Upgrade some dependencies away from vulnerable versions

References:

• Dencun hardfork details
• go-ethereum
• KZG-4844

[b1m0n]

So far this PR lacks of unit tests, for example transitioning from pre-EIP712 to post-EIP712 simulation.

Another big missing is the random value which is serving PREVRANDAO opcode is not properly created in EVM context. Following go-ethereum, this value is calculated each block below

if header.Difficulty.Sign() == 0 {
    random = &header.MixDigest
}

Also could you declare why we need the RANDOM opcode? I see that it's totally duplicated with PREVRANDAO

[khoau2u]

Updated as requested.
Pending full tests.

[trinhdn97]

Need another transient storage reset test like https://github.com/ethereum/go-ethereum/blob/8032b63f167938e6441d4be3eb49b12014d9bfc8/core/blockchain_test.go#L4029

[khoau2u]

I reckon that the TSTORE logic is simple enough that more integration tests are needed instead

[trinhdn97]

Sure we need more integration tests, but the priciple of unit testing is trying to cover more cases. These two method of testing should take different repsonsibilities. So we need to cover as much cases we found out for more code coveraged, as well as detect clashing with future changes

[khoau2u]

Yes, double check is never enough, also prevent breaking changes from passing unnoticed afterward

[trinhdn97]

So far this PR lacks of unit tests, for example transitioning from pre-EIP712 to post-EIP712 simulation.

Another big missing is the random value which is serving PREVRANDAO opcode is not properly created in EVM context. Following go-ethereum, this value is calculated each block below

if header.Difficulty.Sign() == 0 {
    random = &header.MixDigest
}

Also could you declare why we need the RANDOM opcode? I see that it's totally duplicated with PREVRANDAO

We can calculate the PREVRANDAO hash by block events Fantom-foundation/Sonic#266

// GetPrevRandao returns the PrevRandao for current block.
func (b *Block) GetPrevRandao() common.Hash {
	if b.prevRandao == (common.Hash{}) {
		b.computePrevRandao()
	}
	return b.prevRandao
}

// computePrevRandao computes the PrevRandao from transaction hashes.
func (b *Block) computePrevRandao() {
	for _, event := range b.Events {
		for i := 0; i < 24; i++ {
			// first 8 bytes should be ignored as they are not pseudo-random.
			b.prevRandao[i+8] = b.prevRandao[i+8] ^ event[i+8]
		}
	}
}

[khoau2u]

@trinhdn97
We can consider this, but very few dapps use that opcode due to its known weakness (predictability, not manipulability).
Or we could use a timestamp, which wouldn't break the dapp but would be less secure for their rare case.