But still, it is annoying and should be fixed in a correct way (by broadcasting the checkpoint) as otherwise cryptsy could easily reject the 'application'.
The checkpoint is being broadcasted, the checkpoint was updated on 24/12 I'm thinking this problem happens when the cpu gets overloaded during the sync or if memory drops too low, I am looking into the problem and will let you guys know when if I can narrow it down further!
I have another view:
starcoind getcheckpoint
{
"synccheckpoint" : "c51c1e21db4ea688465b72757c578bde94a19a780d376a6fb5997c8b7fa3f8b7",
"height" : 0,
"timestamp" : "2013-07-17 05:52:17 UTC"
}
starcoind getinfo
{
"version" : "v1.6.0.0",
"protocolversion" : 60006,
"walletversion" : 60000,
"blocks" : 419379,
"moneysupply" : 32591791.93443700,
}
It seems you did not get what checkpoint I meant.