Skip to content

PeerDAS: huge till become head #7931

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
twoeths opened this issue Jun 7, 2025 · 2 comments
Open

PeerDAS: huge till become head #7931

twoeths opened this issue Jun 7, 2025 · 2 comments
Labels
meta-bug Issues that identify a bug and require a fix.

Comments

@twoeths
Copy link
Contributor

twoeths commented Jun 7, 2025

Describe the bug

for a super node, it takes > 3mins for a node to become head

Image

Expected behavior

it should be < 2.5s consistently

Steps to reproduce

No response

Additional context

No response

Operating system

Linux

Lodestar version or commit hash

peerDAS
@twoeths twoeths added the meta-bug Issues that identify a bug and require a fix. label Jun 7, 2025
@twoeths
Copy link
Contributor Author

twoeths commented Jun 7, 2025

in this case, nodes have to count on range sync and gossip does not work

Image Image

@twoeths
Copy link
Contributor Author

twoeths commented Jun 7, 2025

as seen on node 2, the reason we can't proceed through gossip is data_column_sidecar messages being ignored

Image

the reason is only parent_unknown

Image

This was referenced Jun 7, 2025
Open
Open
Closed
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
meta-bug Issues that identify a bug and require a fix.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@twoeths