You are viewing a single comment's thread from:
RE: Gridcoin users: check your block hashes -> we just lost 36% net weight in 1h
I observed a similar behavior. The windows seems to stick to a fork a very long time. A reboot usually does fix this issue. I do not know if this is related to the issue of the low net weight.
Interesting thought. Maybe the weight check was removed or something to accommodate for the vastly lowered weight? I would like to see @tomasbrod chip in on this one, he may have some idea of the possible cause.
The wallet will automatically reorganize on the stronger chain after just two blocks if it knows about it and no bad block is found there. But due to way the block Accept code is bugged, blocks received from other (right) chain are often dropped.
That makes a lot of sense. Is this patched in the latest leisure build?
No, unfortunately it is not. It is very hard to do, given the state of the code-base.
If it interests you or any other dev, I think all of us who have looked at the code base would be more than happy to see you bill hours to clean it up further. Even just sensible variable names would make a world of difference.
Agreed. I already started a work on the rewrite and cleanup on separate branch, but it is a very much work in progress. And I don't think I can continue with my school work load, ppl can join :)
hi guys, i had the same problem and a restart didnt do the job for me. i can just underline that obviously the windows wallet does not return automatically or i just was not patient enough. :) Had to reorg the blockchain to a block before the fork happend...
We are having kinda fork issues nowadays or am i wrong ?
We are having worse fork issues - definitely. I doubt the number of forks has changed, but due to the Windows wallet not registering when it is on a fork we are getting much longer forked chains. My wallet has again been on a fork most of the night.
I wonder if people are having a similar experience with the Linux build, or if that still reliably recovers from forks.