seems like mining is stuck at block 4999 for a couple of hours now
Its stuck because difficulty is high and miners left suddenly. It will take time to solve blocks and get it going again.
No, that's not the reason. BCC has been a victim of a
timewarp attack it seems EDIT: The checkpoints are wrong in the wallet. Same thing happened to Aiden.
In fact, this coin has been heavily attacked from day one. No idea why. ON dedicated I've had to mitigate attacks on stratums and web because of this coin. Someone obviously doesn't want it to succeed.
Also - the BCC wallet keeps randomly crashing for no reason. Never had a wallet crash like this. There is nothing in the logs to say why either.
http://bcc.dedicatedpool.comRyan, dedicatedpool.com support/admin
admin@dedicatedpool.com / IRC on freenode ##dedicatedpool
![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2F7yIpdEv.png&t=665&c=UF2zfZYSMfMndQ)
![Sad](https://bitcointalk.org/Smileys/default/sad.gif)
Any help would be highly appreciated!
I would suggest nobody make any transfers until this is fixed. I think because the block will invalidated, that any transfers from wallets will have their coins returned after a reindex of the blockchain, but just to be safe I'll be disabling cron payouts on Dedicatedpool until we know more.
In fact, further investigation of stratum logs reveal this:
2014-04-28 17:15:33,167 INFO template_registry # Yay, share with diff above 100000
2014-04-28 17:15:33,167 INFO template_registry # We found a block candidate! 00000000253f79e4f244e44d678e0bce0c9895b033eb6ae1975d40d1836321a4
2014-04-28 17:15:33,176 INFO template_registry # None
2014-04-28 17:15:33,176 INFO template_registry # New template for 000000000a16fb6ba0850f90e39076092e77eaa96db8a61fd31347179ae14d85
2014-04-28 17:15:33,177 INFO template_registry # Update finished, 0.002 sec, 18 txes
2014-04-28 17:15:33,178 INFO interfaces #
Block eee4e4e1b2ce1f888e79307c612979f2ef60f2e40873972332d8ce24e343dfc5 REJECTEDAnd since it's 4999 and won't go to 5000, there might be something in the code like a checkpoint. When you forked this coin, did you check your checkpoints and make sure they were deleted from the last coin?
EDIT:Here's the problem. You didn't delete the old stake checkpoints from the fork:
Line 24 in kernel.cppstatic std::map<int, unsigned int> mapStakeModifierCheckpoints =
boost::assign::map_list_of
( 0, 0xfd11f4e7u )
( 5000, 0x1d88a220u )
( 10000, 0x3bae1eb9u )
( 15000, 0x8c6b5d66u )
( 20000, 0x90881334u )
( 21330, 0xe07fa575u )
Actually I have to admit, I'm not sure how the "stake checkpoints" actually work, but it seems they are affecting, in some way, the checkpointing for the PoW blocks. I checked checkpoint.cpp and it doesn't have any checkpoints mapped. Anyone else comment on this? I don't have the time right now to look over the PoS code.