Gnosis Pectra fork epoch

[chong-he]

Issue Addressed

* #7274

• Schedule Gnosis Pectra hard-fork #7295

[michaelsproul]

CK do you mind copying across the changes in electra.yaml from here: https://github.com/gnosischain/specs/blob/de1d51759c8bb786c7172740c66ec50cd8cb8d1d/consensus/preset/gnosis/electra.yaml

into consensus/types/presets/gnosis?

[chong-he]

CK do you mind copying across the changes in electra.yaml from here: https://github.com/gnosischain/specs/blob/de1d51759c8bb786c7172740c66ec50cd8cb8d1d/consensus/preset/gnosis/electra.yaml

into consensus/types/presets/gnosis?

The only difference is this first line below:

# `uint64(2**0)` (= 1)
MAX_CONSOLIDATION_REQUESTS_PER_PAYLOAD: 2

which the current LH branch looks correct?

lighthouse/consensus/types/presets/gnosis/electra.yaml

Lines 32 to 33 in aed562a

	# `uint64(2**1)` (= 2)
	MAX_CONSOLIDATION_REQUESTS_PER_PAYLOAD: 2

# `uint64(2**1)` (= 2)
MAX_CONSOLIDATION_REQUESTS_PER_PAYLOAD: 2

If MAX_CONSOLIDATION_REQUESTS_PER_PAYLOAD: 2 is 2, then it should be 2**1 = 2?

[michaelsproul]

@chong-he, good catch, looks like the comment in the upstream Gnosis preset is wrong then

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

• ☑️ test-suite-success

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[michaelsproul]

@mergify requeue

[mergify]

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically