Invalid block signatures

[Zacholme7]

The signature data for the capella block contains non-valid signatures so when we try to parse this data we fail due to bad bls encodings.

[GalRogozinski]

This is odd since this block is copy-pasted and should be valid.
Will look at it later, but are you positive it is invalid @Zacholme7 ?

ssv-spec/types/testingutils/beacon_node_consts.go

Line 5 in dd0581c

// Beacon block taken from https://dora.pectra-devnet-6.ethpandaops.io/slot/58430

[Zacholme7]

The capella block is the one used in the type tests and it conatins invalid signatures.

For example, it has signature":"0x606162636465666768696a6b6c6d6e6f707172737475767778797a7b7c7d7e7f808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9fa0a1a2a3a4a5a6a7a8a9aaabacadaeafb0b1b2b3b4b5b6b7b8b9babbbcbdbebf" which is just a mock increasing sequence.

[GalRogozinski]

@Zacholme7
To be honest I am not sure why this is an issue.
What tests does this break for you?
You just have some default parser from Lighthouse that automatically validates this?
It is hard for you to skip this check?

[GalRogozinski]

It is also possible that we delete Capella blocks since we are past this fork

[Zacholme7]

Hey. this is for the ssz test.

The ValidatorConsensusData gets unmarshalled into the the block. I am using the Lighthouse parsing infrastructure here and the underlying crypto libs we use do not allow the construction of invalid sigs.