-
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
Syncing Issues #3065
Comments
Hi, Neuron includes a full ckb node and a light client node.
If you want to use the light client click |
hello, I wanted to withdraw my ckb from the DAO, but I lost my password, so I created a new wallet. I saw but active and I wanted to update the cache and nothing more it's been more than 2 hours and the synchronization is still at zero someone could help me |
Hi, @Nicko81 Could you upload the Debug Information again? I will check whether the synchronization is still at zero |
Hi, @Nicko81 what is the start block number you set? Could you try to |
Ok I am ah work when I come back at home I look |
Hi,my starting block is 12,466,227 and I just refreshed my cache |
synchronization has just resumed by deleting all data |
Synchronization is 100% but my ckb balance is still at zero, the same for my nervos DAO |
You can help me ? |
Hi, @Nicko81 from https://explorer.nervos.org/address/ckb1qzda0cr08m85hc8jlnfp3zer7xulejywt49kt2rr0vthywaa50xwsqws9clquy8tgjqttltmtuaxntvhp00tg5quxrkav?sort=time I get that your first transaction block number is 12,466,120, so it's better to set the start block number to 12,466,100 and |
thank you very much yanguoyu I found all but balance thanks to the block number that you gave me |
Mark this issue stale because no activity for 60 days |
Close this issue because it's inactive since marked stale |
Topic Type
Cannot Synchronize
Detail of the issue
Taking forever to Sync. Have cleared Cache, updated version restart. Still cannot see my assets. Using Mac
neuron_debug_1709930176383.zip
bundled-ckb.log
No response
bundled-ckb-light-mainnet.log
No response
main.log
No response
status.log
No response
The text was updated successfully, but these errors were encountered: