-
Notifications
You must be signed in to change notification settings - Fork 85
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
The synchronization is very slow #2448
Comments
Maybe because your network is offline when the computer's screen is off. You should keep your network online when |
I have exactly the same problem, my network has been working for 4 days now, it's progressing, but it will take me about 15 days to finalize the synchronization. Apparently many people have the same problem since this version. And all my CKB are still inaccessible for the moment ! |
@S0rci3r The left time is calculated in real-time, and there are many things that affect the sync speed.
And we are researching a quick sync way to use |
Hi @S0rci3r |
No thanks, I'll wait... But why with this version, many people have the same problem? |
Actually, we've received some(several) reports of migration failure before this release, it's a known issue, but no good solutions for now, so [email protected] was still released for necessary updates(use improved ckb-indexer in ckb node for performance and accuracy, removed maturity requirement in dao operations(#2461), some security updates) It's hard to detect if the migration will fail before execution because
What Neuron can do is
Due to our negligence in collaboration and the temporary absence of PM, point 1(notify users about the risk of migration) was mentioned(#2517 (comment)) but not delivered within the application. The caveat was included in Release note / Upgrade caveats
It's true that the channel/method we used is too technical and inaccessible to end users. We will commit more resources to improve user experience. |
Mark this issue stale because no activity for 60 days |
Close this issue because it's inactive since marked stale |
Detail of the issue
The synchronization is very slow, there are already 3 days and only 5% and the percentage instead of increasing decreases
bundled-ckb.log
main.log
No response
status.log
No response
The text was updated successfully, but these errors were encountered: