18:19:00

getblockhash 15213
18:19:00

00000000162ea1f7d2e56600657f052174711511257cd0af27ef04fd48a1c392
Correct?
YES
Dear developers,
Please provide a list of nodes on the correct fork for us to use (via "addnode" or perhaps even "connect" in .conf). Or upload a "correct" blockchain data files.
Today my pool encountered "invalid checkpoint error" again. After deleting data and re-downloading it became normal.
But on my windows machine I deleted, re-downloaded and am getting the "invalid checkpoint error" again!
I assume these problems happen because some nodes are on incorrect fork and it is a matter of luck to which node my wallet connects.
But can't you perhaps increase the protocol version or something similar?
These problems are quite similar to Diamondcoin issues when they were switching to POS+POW.
I remember that they issued a patch to ignore nodes on "old blockchain".
I'm quite worried that even though I'm on correct fork, perhaps in 1 hour I'll hit the "invalid checkpoint".
Thank you
Actually, we've changed the protocol version and are ignoring the older versions. Unfortunately we're experiencing new forks and we're still investigating what is going on. Master Checkpoint Node is trying hard to keep everything together for now.
You can connect directly to one of our pool nodes.
#aidbit.conf
connect=maya.aidbit.net
connect=felix.aidbit.net
connect=kei.aidbit.net
This way you'll limit connection to other nodes.
I know it's frustrating, but it's no better on this side.
Regards,
AidBit