R&D: Supporting blobs

[eyusufatik]

To stay up to date with other EVM platforms, we should support the Dencun upgrade.

The main feature introduced under Dencun is "blobs".

For a centralized sequencer rollup (currently us) it doesn't make much sense to implement any kind of blobs.

But in the future when we have decentralized sequencing it will come in handy.

Another point to consider is how costly KZG commitments are in ZK -- they are enabled by usage of blobs.

So, we can support Dencun without blobs or with blobs. Let's discuss.

[orkunkilic]

I believe we should support dencun if the KZG cost is negligible compared to our current cycle counts. Blobs are pretty much useless atm - but imo keeping the hardforks identical makes sense.

[eyusufatik]

the final decisions on this matter:

• We add blob related fields to the header.
• EVM does not accept any type 3 transactions (txs that carry blob versioned hashes).
• PointEvaluation precompile is not activated.
• Sequencer does not implement any type 3 txs.
• All other dencun opcodes etc. (like tstore) are supported.

[eyusufatik]

Closing discussion with above decisions until we bring additional supports for data blobs.