Enable circuit and contract support for Blob's kzg

[anylots]

Describe the feature you would like

This is an amazing project in the web3 field, And here are some questions and discussions:

How is the progress of Circuits supporting eip4844？ When 4844 is launched, how do we verify that the kzg commitment from the data blob and the kzg commitment from the proof are based on the same txs？

This blog post [https://scroll.io/blog/kzg] discusses the previous plan, but the implementation details of 4844 have been fully determined so far. To achieve this feature, it is necessary to modify the verification contract and zkevm circuit. Now we can try to explore the specific engineering path, which may be helpful in doing something.

Additional context

No response

[ed255]

Currently from from the PSE team we have the "support of EIP 4844" as a low priority in our roadmap.

In the past we discussed how we could use it to achieve cheaper on chain verification of zkEVM proofs. We documented a sketch design to use this in our architecture here https://github.com/privacy-scaling-explorations/zkevm-specs/blob/master/specs/public_inputs.md#public-input-approach Nevertheless we don't plan to implement that approach in the upcoming months. The main reason is that we're not focusing on building a rollup; instead we're focusing on verifying L1 blocks via zk proofs to support zk light clients (so zkEVM proofs verification on chain is not currently a priority for us)

As for verifying blocks that use EIP 4844 blobs, we haven't discussed anything about it. Probably we'll start looking into it once EIP 4844 is scheduled to be included in L1 Ethereum.