Remove kzg point and blob validations in gossip

[pawanjay176]

The c-kzg library has moved to all bytes interface after ethereum/c-kzg-4844#62 which also removes the bytes_to_g1 and bytes_to_bls_field from the public interface.

My understanding is that the conversion function was removed from the public interface since verify_aggregate_kzg_proof will contain the checks for if the commitments and proofs are valid g1 points and each blob < BLS_MODULUS so we do not need to make a separate check.

[dankrad]

Yes, this makes sense. One question is if we should address this:

The KZG commitments of the blobs are all correctly encoded compressed BLS G1 points

Without this check, for any blobs out of the data retention window, there will be no check whether they are valid KZG commitments. We could add a function to check this in the BLS library.

As far as I can see this adds no additional security benefits but wanted to raise it.

[ralexstokes]

Without this check, for any blobs out of the data retention window, there will be no check whether they are valid KZG commitments.

my assumption was that we would not gossip any blobs outside of the availability period, and if so, this would not be a concern as a gossip validation

[dankrad]

Without this check, for any blobs out of the data retention window, there will be no check whether they are valid KZG commitments.

my assumption was that we would not gossip any blobs outside of the availability period, and if so, this would not be a concern as a gossip validation

Blocks are gossiped, and their KZG commitments will not be verified to be G1 points outside this window. As I mentioned, I do not think this has any security impact so I think it's fine to leave it.

[djrtwo]

Blocks are gossiped

blocks aren't gossiped outside of a 32 slot window which is << the pruning window.
so all good