Skip to content

fix: column announcement before fork transition#7943

Merged
matthewkeil merged 1 commit into
peerDASfrom
mkeil/column-announcement-before-fork-transition
Jun 12, 2025
Merged

fix: column announcement before fork transition#7943
matthewkeil merged 1 commit into
peerDASfrom
mkeil/column-announcement-before-fork-transition

Conversation

@matthewkeil

@matthewkeil matthewkeil commented Jun 10, 2025

Copy link
Copy Markdown
Member

Motivation

Column announcement needs to be updated for validator custody prior to fulu fork transition

Relevant spec: ethereum/consensus-specs#4373

@matthewkeil matthewkeil requested a review from a team as a code owner June 10, 2025 09:10
// backfilled the new groups.
// this.custodyConfig.updateAdvertisedCustodyGroupCount(targetCustodyGroupCount);
// this.emitter.emit(ChainEvent.updateAdvertisedGroupCount, this.custodyConfig.advertisedCustodyGroupCount);
if (this.config.getForkSeq(slot) < ForkSeq.fulu) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

need to confirm FULU_FORK_EPOCH is defined first?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we have ForkSeq.fulu that implies FULU_FORK_EPOCH is defined. It can be Infinity though. In that case I think the logic still valid as the current fork will be behind fulu.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nazarhussain not correct, see the spec PR

This new field MUST be added once `FULU_FORK_EPOCH` is assigned any value other than `FAR_FUTURE_EPOCH`.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah @twoeths is correct, we shouldn't advertise this if fulu epoch is not scheduled in the config

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc @matthewkeil ☝️

@matthewkeil matthewkeil Jun 12, 2025

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We discussed this at interop. I will add a change to the spec. It needs to be advertised beforehand for peer management at the transition

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And actually there is another component to this. This change just makes sure the cgc is correct once it gets announced. The announcement is unrelated to this change

@nflaig nflaig Jun 12, 2025

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It needs to be advertised beforehand for peer management at the transition

but this is still the case as soon as we set the fork epoch value, in practice this will likely 2-3 weeks before the fork happens

@matthewkeil matthewkeil merged commit 23530b6 into peerDAS Jun 12, 2025
17 of 18 checks passed
@matthewkeil matthewkeil deleted the mkeil/column-announcement-before-fork-transition branch June 12, 2025 09:56
@twoeths

twoeths commented Jun 13, 2025

Copy link
Copy Markdown
Contributor

NetworkCore.onEpoch() seems to be a better place to do this instead of chain finalized event
need to revisit this later

matthewkeil pushed a commit that referenced this pull request Jun 13, 2025
**Motivation**

Follow-up PR to #7943.

As per spec
> This new field MUST be added once `FULU_FORK_EPOCH` is assigned any
value other than `FAR_FUTURE_EPOCH`.

we should only announce these if fulu is scheduled in config

**Description**

Only announce columns if fulu is scheduled in config
@wemeetagain

Copy link
Copy Markdown
Member

🎉 This PR is included in v1.34.0 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants