This repository was archived by the owner on Aug 18, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 631
[explorer] updateAddrBalances: attempted to subtract {X} coin(s) from address {A} which only has {Y} coin(s) #3409
Comments
Are there any updates on this? Our node can't finish syncing as it crashes every few minutes due to this error. |
I have the same problem, unfortunately. |
Same here, only for me the node doesn't crash, but it starts using a lot of resources (cpu,mem,disk), and then I need to kill it. |
Update: was RAM issue. Once increased from 8GB to 16GB - it worked. |
I am currently working on debugging an issue closely related to this. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello!
While syncing the explorer node I often see these error messages, like:
Node keeps syncing after reporting it, and looks like everything works fine.
Is this ok? How there can be a historical attempt to subtract something invalid? If a transaction is invalid - it wouldn't be included in the chain; and if a transaction is in the chain - shouldn't it be guaranteed to be valid?
Doesn't it mean that the explorer node accounts addresses wrong?
For example, if we check out a summary for one of these addresses and compare it with alternative explorer:
Official one shows 109 transactions and balance of 7,217.944985 coins (at the time of writing) - http://cardanoexplorer.com/api/addresses/summary/DdzFFzCqrhtB66YkKzouHqeTAznkyCL7xfwAZvrgqkGiqhkjBcLSV3D8hCn9Ug7xBrpXwHEukKoWJq1w6cdh1a2Nt6fGp3M5tVocVPSV
Alternative one shows 3881 transactions and balance of 134,350,983.923166 coins (at the time of writing) - https://adatracker.com/address/DdzFFzCqrhtB66YkKzouHqeTAznkyCL7xfwAZvrgqkGiqhkjBcLSV3D8hCn9Ug7xBrpXwHEukKoWJq1w6cdh1a2Nt6fGp3M5tVocVPSV
It really does not look good.
This issue is critical, because it's the REFERENCE EXPLORER, and the whole community relies on it for checking the validity of information.
The text was updated successfully, but these errors were encountered: