Thanks everyone and all that sent me encouragements.
I found the issue of pos, why it is stopped. It related to the issue that network time sometimes messed up.
For pos, the last pos block (block 62235) has a network time before the previous pos block (block 62234), this messed everything and caused the pos generation does not meet the criteria so it is rejected:
>> Height = 62235, fProofOfStake = 1, nActualSpacing = -575
>> pindexPrev->GetBlockTime() = 1388562077, pindexPrev->nHeight = 62235
>> pindexPrevPrev->GetBlockTime() = 1388562652, pindexPrevPrev->nHeight = 62234
I have a fix for that, and it works in my test (generated pos block again). But this is a hard fork. I will provide a new version of the client, and it is a
mandatory upgrade. I will give about 3 days before the switch over happens. Before the switch over happens, the coin will generate only the pow blocks (as it is now).
The same issue seems occur at pow block, that's why sometimes in block explorer you will see the time messed up. I do notice that this occurs in many other coins. In general this will not cause much problems, but sometimes it could cause diff behave strangely (usually transient). The network time issue is a broader issue which may need some revisit on the fundamentals of the cryptocoin, which I will not address now (this will require a lot more work and maybe a team work).
With my fix, the next time network time issue in pos should not cause a stop in pos generation.
A new version of the client will be provided some time later today or tomorrow.
