New builds up. Primary change as that win64 should work better. With any of these builds you will need to delete data directory or run with -resync due to change in the transaction database.
Current is 14071622
@Billotronic that is good you have machine running for extended time. I have noticed a bug, it was in QT, but probably also in CLI. You can kind of see if it's happened to you from the
Update: 11659 11659 11659 11659 1
lines that are printed. When the bug happens, the third number will be less than the 4th by large amount. So like
Update: xxxxx xxxxx 10559 11659 x
Otherwise, the client will appear to be operating normally. Mining may work, transactions will be sent and received, no crashes, no errors. I think this is why there have been no reports. Restarting the client fixes it, I accidentally did that the last 2 times this bug happened. So if you see it, please grab a log before doing anything else. This bug is very serious, show stopper style as it can and will cause large scale forks. Currently no way to reproduce it and very little data on what is actually happening.
How large? I just killed the client to update and this was the last line:
Update: 11759 11759 11675 11759 1