Until there is a proper fix that can let the client sync from block 00001 there willbe no active chainstate.info.
Even with a proper fork as upstream (connect=) the syncing keeps stuck at block 34001 (as i need to sync it from the start because of daemon patches)
I dont know how the dev did it but this fork messed up big.
Will come back when things are stable again..
I don't know why anyone even installs these hardforking updates. The previous releases already showed that this coin lacks core developers able to handle slightly intrusive updates without severely messing up things, so responsible users should always try updates on a testnet first.