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

node consistently 12 hours behind #8978

Open

MrFrogoz opened this issue Jan 12, 2024 · 5 comments

Labels

C-bug S-unconfirmed

MrFrogoz commented Jan 12, 2024

base-org/node#127 (comment)

Author

MrFrogoz commented Jan 13, 2024

base-org/node#127 (comment)

Author

MrFrogoz commented Jan 13, 2024

base-org/node#127 (comment)

0xChupaCabra commented Feb 4, 2024

same problem here, my two optimism nodes are always 12 hours behind

smartcontracts added C-bug S-unconfirmed labels

Contributor

smartcontracts commented Feb 5, 2024

Can you check if this comment is relevant to you? base-org/node#127 (comment)

Jonney commented Feb 15, 2024 •

edited

Perhaps a block time of 4-6 seconds can solve this problem. base-org/node#127(comment)

A 2-second block time will cause 3 issues:

Longer recovery time after node restart.
Longer recovery time after chain reorganization.
Higher network performance requirements, consistently 12 hours behind.

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