Another clue:

https://bt.irlbtc.com/view/279601.msg3270196#msg3270196

Too many POS blocks being generated by a pool. Pos is taking priority rules and blocking All POW generation.


Next clue :

https://bt.irlbtc.com/view/279601.msg3273614#msg3273614



and finally (maybe) :  https://bt.irlbtc.com/view/279601.msg3275100#msg3275100

possible fix...renew coin-age in large wallets by moving coins to another address/wallet..send to self etc...this will knock down the POS generating override and allow POW to be mined once again.

The longer you keep a coin in your wallet...the more likely it will generate POS...and block  POW generation.


Hope this helps.

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.  

AFAIK.  It depends on how the coins arrived at that wallet, as the PoS is purley based on time or blocks passed since generation.  So for example blocks that were originally solo mined will stake one at a time, but if you get 1000, in one lump from a pool it will stake as one block in the future. 

I have not had darsek show stake ever.  UFC does all the time and shows it. How many coins do you have to have before it does its thing?

I wonder if we could try out a system similar to proof-of-burn here. Basically, you prove that in the old blockchain you sent coins (from an address you own) to an unspendable address (and that that event actually occurred), and that gives you new coins.

I'm not sure how feasible that would be, though. You would need to get a full record of unspent txouts, as well as give people time. A complete cross-reference would also be advised.

The superblock idea, though, looks good - mine a few superblocks corresponding to the entire KED supply and send it to the addresses containing KED.

@ Dreamwatcher.

1.  Thank You for all your help and support, you truly are the main reason for the success of these coins.  I think I speak for everyone when I say this.

2.  I had already considered the hard fork option, but like you pointed out the dev time needed is high, and most importantly there is no guarantee of success.

3.  I personally want to do a relaunch and give coins back in the amount, that they have currently been mined.  I want a block of 100,000 to devide and the remainder used for a design competition.  To redesign the darsek logos, so that it truly is distinguishable from the original.

4.  If we do go down this route, It would be good to know if the ked explorer http://ked.cryptocoinexplorer.com/  can be used to see all wallet balances.  People would stake their claim on the forum (we could use the new www.scificointalk.com *thanks to Shad3dOne*) to each balance and I will manually payout at launch.  Unclaimed balances will remain for  1 or 2 months and then if unclaimed we can give them away.    We *could* do it by people sending in their current coins, but we are running out of PoS blocks to process the transactions, so best to do it the way I suggested.



Maybe we will need to have a poll, to determine what people want from the new coin.  What algorythm? what style? base58 starting letter, total coins, block target time, TX comment needed?  TX fees?  Maybe to make it indivisible like pennies or some other Ideas.

I believe it only happened to PoS coins that are not on an exchange before PoS kicks in.
Once it is on an exchange, people will start moving coins and less PoS blocks are generated.

i figure 3-5 days before the networks starts flowing freely again.

there is quite a backlog of POS blocks trying to squeeze through the little KED network's CPUs. and since there is no effective way to cancel a current minting POS block (that i know of).. just gotta wait till you're CPU is done ....then your reservebalance function should kick in.

once the network grows and there are more transactions between addresses...this should not be an issue?

cheers

How about encrypting the wallets? will that stop the POS?