Deneb Support

[MatheusFranco99]

Major changes

• Added logical support to Deneb's beacon block in consensus data.
• Note: When submitting a proposer duty output (VersionedProposal or VersionedBlindedProposal) to the Beacon node, Deneb uses:
  • VersionedBlindedProposal: a BlindedBeaconBlock, similarly to other forks.
  • VersionedProposal: BlockContents, differently from older forks which used BeaconBlocks. Nonetheless, the validator signature is still over the beacon block (BlockContents.Block), i.e. the signing root is kept the same.

Minor changes

• Updated Attestantio lib from 0.16.3 to 0.19.7. Purpose: use up-to-date Deneb spec types.
• Updated Fastssz from 0.1.2 to 0.1.3 as a consequence of the Attestantio update.
• Deneb testing utils. To-Do: define Deneb fork epoch.
• Added type tests.
• Remove all Bellatrix objects and use Deneb.
• Update ssz-max sizes for ConsensusData and FullData fields, since Deneb uses a BlockContents object which contains a Beacon block, KZGProofs (288 bytes) and Blobs of 786432 bytes.

SSZ generation notes

• Fastssz 0.1.3 is now deterministic. Because of this, when you run make generate-ssz you may see new logs INFO: Skipped ssz generated object:.
• Fastssz 0.1.3 seems to have an error which occurs in the consensus_data_encoding.go file. It imports an unused library. For that, we created an issue in Fastssz which remains unsolved. As a temporary arrangement, we added, in the generate.go in ./types, a command to remove the unused import.

Attestantio update notes

• The default DataVersion used to be phase0. This was was changed to become unknown. Therefore, some testing utils that didn't define the DataVersion in the ConsensusData had to be updated.

Leftovers To-Do

• [x] Set the correct Deneb fork epoch.

References

• Deneb Consensus-Spec

[GalRogozinski]

There seems to be some epoch activation epochs here

Not sure if it is final but maybe let's put this in and later change it so we can all approve this PR

[MatheusFranco99]

@GalRogozinski If I update it, I start getting:

panic: can't start new duty runner instance for duty: input data invalid: duty invalid: duty epoch is into far future

because of the dutyValueCheck.

[GalRogozinski]

Closes #219