Duplicate Blocks in blockchain.

2654093 44351067955186c77c7e44354b05200dcdf951d3046b7f2414f9798218dd498a 2 45046.63893600 Wed, 31 Jan 2018 19:03:38 GMT
2654093 cbbdabf8f071ef02f79d7c23b9ddd6bc74bea15c8e99f5a92a75370b7267da32 2 45387.95703600 Wed, 31 Jan 2018 19:03:38 GMT
2654093 40a7553e14857887228dd573417ba2abb9954b3cf008553cf3cdf24de6b2760f 1 1391693.18953500 Wed, 31 Jan 2018 19:03:38 GMT

Those are transactions of one block that is orphaned according to your explorer.

The block is

Code:

be4081a8b549f0d22c9a5deffbfcce96ceb3828a2425b7c9f1adce6249fa9f97

The current valid block is

Code:

5051737cc4f965034e3c5565853c05d42af21baf62e2232b5e6101710c30e4c6

I'm assuming that block height 2654093 are POS blocks. As I run a full node and the height is only at 2629568 at the time of writing this. Cryptopia also reports the height at 2628045 when they put their node into maintenance mode "21/01/18 - Investigating Deposit issues. Rebuilding wallet." It seems that no one was mining the coin. I started mining to keep the coin alive.

I got interested in this ordeal when I added paccoin to the pool I've been developing for a year for testing. As well as the volume of trades at Cryptopia in the first few days of release. I've also been watching the announcement thread with astonishment to how the situation is being handled. I'm assuming that you're trying to figure out the issue that was stated in pull request #12.

My suggestion for the whole ordeal is to be able to replicate the issue in an controlled manner. Add regression tests to check for possible problems that can arise. Thus having better quality control for the main chain. The first step is to add an regtest mode just like bitcoin has.