Quote from: seasonw on September 11, 2017, 01:40:40 AM

1. After F7000, I noticed a lot of these message, what is this about?

2. And I have a machine in ubuntu stopped working after 7000, I restart it, error message said index database corrupted, I removed .biblepaycore and reload all database, but it stucked at 7022, same message as SquidConqueror did. Then I did a tricky solution which is to copy .biblepaycore from my other ubuntu machine, problem solved. But then my hashrate dropped from 400k to 40k, my other machine remain same hashrate as previous.

3. I restart wallet in my i7 windows machine, hashrate dropped from 160k to 5k, whereas my other windows machine remain same hashrate as previous (I did not restart the wallet). And yet, after restarting my i7 wallet, it is very laggy, some new calculation required more cpu power?

Thanks Wink

Regarding the Invalid solution, its only happening about 1 in 100 hits to the pool. Im going to be giving a technical reason soon, but the short answer is it should go away at block 7256.

Regarding index database corrupted, same problem, should be a short term problem until 7256. Ill explain in a minute.

Regarding the hashrate: The problem is the big dogs have a RAID advantage because they have SSDs and multiple disks. The small guys have a single debug.log. We are spamming the log, and slowing the hashing down.

More in a minute.