Ok guys so the reason for the Darsek problem is quite simple from what I seem to be seeing, and as you may have gathered I have nowhere near the level of understanding of the complexities as Dreamwatcher does.  However, this is not a problem in the code as such but more of a circumstantial issue.

The daemons and QTs that have long term static coins are crashing and taking up a vast amount of resources. This is also probably the reason Dreamwatcher has problems with the darsek pool daemon.   The stake blocks are a big issue on resources especially as some of you have vast amounts of coins.  

The long term solution (if you still want to store vast amounts of coins) is to either move them around, or store them on a client that is always on and not in cold storage, this will take a lot of processing power if you have a large amount of coins.  

In the future this should, in theory become less of an issue as the coins with have more liquidity and as a result less PoS blocks with a stronger network.  

The reason we are seeing problems now is because many people will have re-synced old wallets after the new clients were released.  the PoS blocks are all bottle-necking the network as they have been stored up for a long time.  Now all this info is being forced onto the chain.  

Like  Shad3dOne has suggested the only fix now is to move your coins along to completely new client (wallet.dat) .

You may find that moving them is a pain, but keep trying and you will get there.  


I may be wrong.