The client is bugged and weighted to those with the most coins. There's is a coding error in the SetBestChain logic which results from several bugs in the way the 'trust' value is calculated. You can see the code here:
https://github.com/wmcorless/paccoin/blob/master/src/main.cppline 2047:
if (pindexNew->bnChainTrust > bnBestChainTrust)
The glitch allows PoS blocks to "reset" the chain. You can see the impact by blocks erasing, transactions going into the void (aka. confirmed and then 0'd out), and PoW blocks disappearing into the void also. it even eat other PoS blocks. The net result is that 'old' account with more stake are able to nuke new PoS, PoW, etc. which is, obviously, not right.
Luckily, the fix is simple, only accept new PoS blocks when when their height is higher than the previous block.
if (pindexNew->bnChainTrust > bnBestChainTrust && pindexNew->nBestHeight)
Now the devs just need to make it. If not, I'll post a hardfork shortly for anyone interested in a fair coin. I mined pac the day it was launched years ago and while I applaud the new launch, this needs to be corrected.
Right now, however, the largest wallets are issuing PoS blocks out of sync by several hours but they reset and fork the chain because they have a higher 'trust' score despite being several hundred or thousand blocks behind.
This is all easily observed on the blockchain explorer look at blocks:
http://paccoinexplorer.com/block/356b009bdda2c826b57b973c753705dc0ac822bd720c7047e0fc3c5f28a81b68and
http://paccoinexplorer.com/block/ba33cb2c216b4574ea191cadfc678e01608d085eaa2f1beb7f45921a55374fd9The second block came first in time with a much higher height which should have controlled the chain but the link above it actually reset the height by 15 blocks erasing any PoW, PoS, and TX mined during that time.
I've been watching for a few days. If you want to observe the behavior yourself because you don't trust me (I've been a blockchain dev since long before pac actually launched) you can view the output of the latest wallet in the debug.log. Search for SetBestChain(). When the chain forks due to a PoS trust block eating previous blocks you'll see the height drop:
SetBestChain: new best=00000000000d44d98ce9 height=2622715 trust=4070805786459404226 date=01/13/18 22:53:05,block hash= 00000000000d44d98ce9fa105c6f11210ece856c62d814ba5026c11db590ce85
SetBestChain: new best=1e775ca1297f46d905c6 height=2622707 trust=4070805893862858138 date=01/13/18 22:50:10,block hash= 1e775ca1297f46d905c60735ef28fbf8aeb3102be98c7f144f39b5c4ecd6d2b4
Anyway, if the devs don't want to patch the forking issue, I will and I'll post a new wallet for anyone interested. I'd like to keep one chain but that chain needs to be fair for all of those invested.
...at least that's what I believe...