-
Notifications
You must be signed in to change notification settings - Fork 83
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
[Bug Report] **Please describe the bug shortly** #3241
Comments
Hello, I had ckb in my bitpie wallet, and its withdrawal was closed, and I started recovering with the 12 private words I had in the neuron wallet, and I did it through the lighet client, and all the blocks were completed 100%, but unfortunately, I still have the balance. It shows zero |
@Bahadorshabani |
Now the problem is that it shows zero balance after completing the blocks |
I will send you a message via mobile when I enter the setting |
@Bahadorshabani Hi, I didn't receive the image, it uploads failed. |
|
@Bahadorshabani Could you upload the Debug information of the native wallet? it can be exported by Menu => Help => Export debug information. I can not get the problem only from the picture. |
Does it mean that I enter the help section from inside the computer? |
That's right |
I simply don't know |
Please select the Export debug information from Help in the top menu. A zip file should be generated, it includes log files of Neuron. Please send it to [email protected] and we can try to find how to fix it. |
It shows zero balance |
good evening team |
Topic Type
Incorrect Balance
Detail of the issue
Hello, I had ckb in my bitpie wallet, and its withdrawal was closed, and I started recovering with the 12 private words I had in the neuron wallet, and I did it through the lighet client, and all the blocks were completed 100%, but unfortunately, I still have the balance. It shows zero
adres
ckb1qypqytypq6clg8z4e5pv2y78lgrzl7unu3hqe2t7gp
bundled-ckb.log
No response
bundled-ckb-light-mainnet.log
main.log
No response
status.log
No response
The text was updated successfully, but these errors were encountered: