Thanks for the reply, yes I keep the wallet offline most of the time since i don't have enough Pivx for staking purposes. My guess is that since my wallet was offline at the time of the zerocoin implementation, I had no Pivx converted to zPiv (not 100% sure, though). Keeping it offline until the next update comes out and then I'll sync it again.
good plan
@btct22 no i don't use slack anymore (was schocked when I was there, lots of idiots
)
will wait for 3.03 and i just saw this tweet:
https://twitter.com/_pivx/status/921291418815123456FYI:
NewsATTN: Block chain inconsistency caused a split chain. New wallet to be released shortly. (self.pivx)
ATTN All
With any major technical innovation, some issues are bound to happen and therefore the Devs do extreme testing on many levels. That said, an anomaly occurred after the launch of the 3.0.2 core wallet, causing a split chain to form. Developers monitoring the blockchain immediately noticed this event and have now notified all exchanges. Users funds remain safe how ever as standard precaution are reminded to make a new backup of their wallet.dat file. A new checkpoint was added that will guide the new wallets onto the correct chain. Compiled binaries for PIVX Core wallet version 3.0.3 will be made available soon after.
Next Steps:
Backup your wallet.dat
If you are currently running 3.0.0, please do not upgrade to 3.0.2 or make any further transactions.
On release of the stable wallet release, upgrade to the new wallet then reindex your blockchain to ensure that you are on the correct chain unless you know how to check beforehand.
Running "reindex" from the PIVX Core 3.0.3 debug console will return you to the correct chain after updating.
Wallet links will be avaible soon. Thanks for your patience during this bit of a rocky transtition. Don’t worry, we are working around the clock on these things to ensure the wallet’s integrity. And with this nailed down, we can move on to other amazing projects and features for PIVX!
Source:
https://www.reddit.com/r/pivx/comments/77knl3/attn_block_chain_inconsistency_caused_a_split/