header changes

[vbhattaccmu]

Pull Request type

Please add the labels corresponding to the type of changes your PR introduces:

• Feature
• Bugfix
• Refactor
• Format
• Documentation
• Testing
• Other:

Description

Related Issues

Testing Performed

Checklist

• I have performed a self-review of my own code.
• The tests pass successfully with cargo test.
• The code was formatted with cargo fmt.
• The code compiles with no new warnings with cargo build --release and cargo build --release --features runtime-benchmarks.
• The code has no new warnings when using cargo clippy.
• If this change affects documented features or needs new documentation, I have created a PR with a documentation update.

[ToufeeqP]

Where are we publishing the commitments now so that light-nodes can use them while validating the ev-proof & sampling?

[ToufeeqP]

@vbhattaccmu Validators should still validate the fri_proof of all the blobs in a block.

[ToufeeqP]

And we also need to validate the commitments root that the block authoring node generates & puts in the header