Skip to content
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.

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

node consistently 12 hours behind #467

Open
MrFrogoz opened this issue Jan 12, 2024 · 5 comments
Open

node consistently 12 hours behind #467

MrFrogoz opened this issue Jan 12, 2024 · 5 comments

Comments

@MrFrogoz
Copy link

base-org/node#127 (comment)

@MrFrogoz
Copy link
Author

@MrFrogoz
Copy link
Author

@0xChupaCabra
Copy link

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

@smartcontracts
Copy link

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

@Jonney
Copy link

Jonney commented Feb 15, 2024

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:

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

@tynes tynes transferred this issue from ethereum-optimism/optimism Jun 17, 2024
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

No branches or pull requests

4 participants