Quote from: BitcoinFX on January 11, 2015, 10:49:02 PM

PoS function has not been removed from the code. It has only been temporarily deactivated by enforcing reservebalance= large balance to prevent staking coins in the wallet.

I like that even better, because it might be easier to "restart" an adjusted PoS process than to create a completely new one. It might be done without a hard fork as exisiting clients already deal with PoS blocks.

Quote from: BitcoinFX on January 11, 2015, 10:49:02 PM

It is therefore still possible to stake (if you edit before compiling) the code or to fully reactivate staking in the future.

That - especially the latter one!

Quote from: BitcoinFX on January 11, 2015, 10:49:02 PM

Staking (or having 3 methods of block generation active at once) seemed to be causing some issues as the block chain increased in size. This was simply part of a fix to get the chain moving again following multiple 'forks'. Staking does still appear to stall the client on occasions though. I suspect its rather like the old expression "two's company, three's a crowd" ? Grin

I'm aware of the problems this has caused until PoS was effectively deactivated. Having a second process that secures the block chain might not bad, though.
It allows removing (or significantly lowering) the PoW block trust values while still having two processes that can create blocks with a reasonable trust value.
I doubt that this is really necessary if PoB works as intended. But having a reinsurance rarely is a bad idea Wink