Are you sure?
Yep. I think that immediate check pointing policy is evil.
Agreed. That is why the block depth is set to 3 when ACP went live rather than 0 based on feedback from technical users in the crowd. This allows some natural reorgs.
After updating. They were the first two blocks found after we updated.
Can you get me the times and block numbers?
I would like to find out why this did not work.
Feathercoin version v0.6.4.4 (2013-09-19 10:40:03 -0700)
Startup time: 09/30/13 06:42:48
[...]
ThreadRPCServer method=submitblock
ERROR: AcceptBlock() : rejected by synchronized checkpoint
ERROR: ProcessBlock() : AcceptBlock FAILED
[...]
trying connection 195.59.191.91:9336 lastseen=2.1hrs
SetBestChain: new best=96756968b3c40a36bd2d height=88291 work=36701685832636670 date=09/30/13 17:22:21
[...]
ThreadRPCServer method=submitblock
ERROR: AcceptBlock() : rejected by synchronized checkpoint
ERROR: ProcessBlock() : AcceptBlock FAILED
Flushed 11448 addresses to peers.dat 95ms
connection timeout
trying connection 98.180.48.36:9336 lastseen=13.3hrs
received block f9f880425fe123ef8908
SetBestChain: new best=f9f880425fe123ef8908 height=88387 work=36774223244962492 date=09/30/13 21:33:26
SetBestChain: 21 of last 100 blocks above version 1
ProcessBlock: ACCEPTED