Implement Blob transactions (type-3)

[Nashtare]

First part of dealing with #41

• Implements blob transactions (type-3)
• Adds new block header fields related to blob gas market
• Implements BLOBHASH opcode

It doesn't deal with the actual blob gas market, this is low priority, though could be tackled in the future if judged necessary.

Once #46 is done, we could add a similar test than evm_arithmetization/src/cpu/kernel/tests/transaction_parsing/parse_type_0_txn.rs but for type-3 easily.

[Nashtare]

Unrelated, but another tiny oversight of 0xPolygonZero/plonky2#1313

[hratoanina]

Partial review.

[hratoanina]

Finishing my review.

I think some part of the block circuit logic is missing, namely the updating of the blob excess gas in connect_block_proof.
Apart from that, looks good, thanks!

[Nashtare]

I think some part of the block circuit logic is missing, namely the updating of the blob excess gas

Do you mean the enforcement that the value is consistent with the parent block excess gas + blob_gas_used? I'm not sure this is really relevant, as we don't enforce anything on the blob gas market logic anyway (at least now). Or did you mean something else?

[4l0n50]

Maybe you can add an interpreter test for this function?

[4l0n50]

Once #46 is done, we could add a similar test than evm_arithmetization/src/cpu/kernel/tests/transaction_parsing/parse_type_0_txn.rs but for type-3 easily.

I don't understand why would you need the evm tests for cancun for the type 3 parsing test. Is it for avoiding using py-evm?

[Nashtare]

Once #46 is done, we could add a similar test than evm_arithmetization/src/cpu/kernel/tests/transaction_parsing/parse_type_0_txn.rs but for type-3 easily.

I don't understand why would you need the evm tests for cancun for the type 3 parsing test. Is it for avoiding using py-evm?

I meant to easily test. Ideally (probably not worth doing it on the current main branch), with the Cancun branch, we should have more hardcoded tests from the official Ethereum test suite that we just deserialize and run in our CI. It's cleaner and easier than crafting our own tests that are unofficial.