-
-
Notifications
You must be signed in to change notification settings - Fork 696
fixUtxo - flag logs need more information for blockbook fix UTXO #1252
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
Comments
we get the following repeatedly: Blocks 1000: alternative 1000, conservative 1000, economical 1000 |
After running utxo fix it took one and half day for BTC:
When i start with -fixutxo=false i got following logs, this means should i run fix again? I understand that out of 22792 errors fixed 2479. Or should i leave it with false for sometime?
|
Also noticed that all negative balances resetting to zero.
|
Ahh, the negative balances cant be fixed ? is that the reason we got this ? |
@martinboehm , is the -fixutxo=true is a onetime fix for utxo? or how can we know we should run this fix? I understand that after we start the blockbook service with option -fixutxo=true we should wait until it gets completed. But I want to understand is this one time fix? Lets say i have the following logs when the fix is completed which means -fixutxo=true
This means that scanned rows should be scanned again? In my opinion it should scan again, but is there a way to check faster? or from some block to some block? |
This should be a one time fix. It should not be needed any more, it was used a long time ago as a fix to a bug... |
added option -fixUtxo=true, to fix utxo transactions, it would be great if the logs shows how many rows left and how much ETA or aleast per block how much time it took all that.
The text was updated successfully, but these errors were encountered: