Since this hard fork, all pools and exchanges appear to have shut down to sync back up I assume.
https://medium.com/@cryptocayce/incident-pinkcoin-network-attack-9f6bbe5048b6
The attackers found a vulnerability that allowed them to produce a large number of blocks and make them appear to be created in a very short period of time without increasing their difficulty.
We believe a block difficulty validation routine vulnerability was the cause of exploitation.
This led to a rush of new blocks at a lower difficulty, allowing the attacker to generate pinkcoin.
The attacker ‘rewound’ honests blocks after 315055 to seize control of the chain.
All your pinkcoin are safe, and no coins were stolen in this attack.
The network was hardforked with a new protocol revision number at block 315065.
The HF fixes the time-warp difficulty adjustment bug, and undoes all the dishonestly mined blocks.
Any transactions after this height (2017–12–22/23) will need to be resent to the network to be processed.
We are coordinating with exchanges and miners with the updated wallet.
Please update to Pinkcoin 2.1.0.3, this is a mandatory HF to mitigate an active attack against the Pinkcoin Network.
Post-Update steps
Remove any old ‘addnodes’ in your pinkconf.txt
Delete peers.dat from your .pink2 datadir. These stale peers may be running older versions. Let it get new peers from DNS/new network
When running, rescan the blockchain from the HF height:
./Pinkcoin-Qt -startfrom=315065
or
Pinkcoin-Qt.exe -startfrom=315065
For a visual on how to do this check out our blog post here