-
Notifications
You must be signed in to change notification settings - Fork 402
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
Nethermind is not syncing old blocks on Ropsten #4189
Comments
We are investigating it right now |
@marcindsobczak Thank you! Please let me know if you need any more info from my side. |
@gituser got a positive response from @marcindsobczak that it looks fixed in master, we are doing more testing and want to release it next week. You can use experimental version for now. |
@LukaszRozmej thank you for the update. It seems to be working with lighthouse after numerous tries of resync.
also maybe get rid of these lines, as this server is no longer working (ropsten-stats.parity.io):
|
Thank you for feedback. We have not enabled SnapSync as a default mode yet because of some issues with post-merge sync, but at this point I think it's good idea to make this change. Merge TTD is not needed in the config - it's already hardcoded. I will create a PR with SnapSync as default and EthStats removed |
I'll close this issue as I was able to sync all blocks on Ropsten with Lighthouse CL with the latest Nethermind built from master (d433fcf). |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
v1.13.3
nethermind version and sync ropstenlighthouse v2.3.1
Expected behavior
Nethermind should be synced completely.
Additional context
Here is my config:
The text was updated successfully, but these errors were encountered: