Update to new version of jc-kzg-4844 lib

[vaidikcode]

Signed-off-by: vaidikcode [email protected]

PR description

Updated all the related dependencies

Fixed Issue(s)

fixes #7848

Thanks for sending a pull request! Have you done the following?

• Checked out our contribution guidelines?
• Considered documentation and added the doc-change-required label to this PR if updates are required.
• Considered the changelog and included an update if required.
• For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Locally, you can run these tests to catch failures early:

• unit tests: ./gradlew build
• acceptance tests: ./gradlew acceptanceTest
• integration tests: ./gradlew integrationTest
• reference tests: ./gradlew ethereum:referenceTests:referenceTests

[siladu]

Hi @vaidikcode can you outline any testing you have done for this please?
I am wondering if we need to check there isn't a performance regression.

[siladu]

From https://github.com/ethereum/c-kzg-4844/releases/tag/v2.0.0 sounds like there could be some negative memory impact along with the speed improvement

Compared to precompute=0, precompute=8 is ~75% faster but uses 96 MiB of memory.

[vaidikcode]

Hi @siladu ,
I didn't pay much attention to the precompute value when I updated the dependency; I followed the recommendation from the official dependency website. However, now that you've mentioned it, I realize it could significantly impact memory usage. What do you think I should do next?

[fab-10]

Teku already did the update Consensys/teku#8651, so we can ask to @StefanBratanov insight about the possible memory impact

[StefanBratanov]

Teku already did the update Consensys/teku#8651, so we can ask to @StefanBratanov insight about the possible memory impact

This value is for PeerDAS, I was told to have the same memory footprint as previous ckzg versions should set the value to 0.

[jflo]

I'd like to put this on hold till we can verify the dependency via verification-metadata.xml

[jflo]

confirmed, this looks good thanks

[siladu]

@vaidikcode there's some failing tests, could you try to reproduce locally please?

[vaidikcode]

@siladu working on it

[fab-10]

Remove the version where not needed, and according to the c-kzg-4844 changelog

The trusted setup format has been updated to include G1 points in monomial form.

This version of c-kzg-4844 requires the new trusted setup file.
The new trusted setup file can be used with previous versions of c-kzg-4844.
Download the new file from [trusted_setup.txt](https://github.com/ethereum/c-kzg-4844/blob/4b915a6617a85ef8c49d456374c1bc7f8647d968/src/trusted_setup.txt) in this repository.
This should match [trusted_setup_4096.json](https://github.com/ethereum/consensus-specs/blob/13ac373a2c284dc66b48ddd2ef0a10537e4e0de6/presets/mainnet/trusted_setups/trusted_setup_4096.json) in the specifications.

So I expect that the trusted setup file should be update as well, @StefanBratanov was that the case in Teku?

[fab-10]

the version is defined in the platform project, so it needs to be removed here

[fab-10]

remove the version

[fab-10]

remove the version

[StefanBratanov]

Remove the version where not needed, and according to the c-kzg-4844 changelog

The trusted setup format has been updated to include G1 points in monomial form.

This version of c-kzg-4844 requires the new trusted setup file.
The new trusted setup file can be used with previous versions of c-kzg-4844.
Download the new file from [trusted_setup.txt](https://github.com/ethereum/c-kzg-4844/blob/4b915a6617a85ef8c49d456374c1bc7f8647d968/src/trusted_setup.txt) in this repository.
This should match [trusted_setup_4096.json](https://github.com/ethereum/consensus-specs/blob/13ac373a2c284dc66b48ddd2ef0a10537e4e0de6/presets/mainnet/trusted_setups/trusted_setup_4096.json) in the specifications.

So I expect that the trusted setup file should be update as well, @StefanBratanov was that the case in Teku?

Yes. It was updated. The new one is in the repo itself.