Quote from: slimcoin on July 09, 2014, 05:19:40 PM

I just finished implementing the bigger updates for PoB and PoS, etc.

I still want to test the changes, so I will not release them yet.

Here are the changes:

PoB difficulty is now target based and targets to be found 1 every 3 PoW blocks.
PoS difficulty base was increased to that of Novacoins'.
PoS reward was increase to 10% to compensate for the increased difficulty and make it worth minting (because with 1%, the reward is dust)

PoW, PoB, PoS block "trust" values were adapted to that of Novacoins'.
Previously, PoW and PoB blocks had a trust value of only 1 while PoS trust values were much larger. Now, all block types have a better calculated trust value.

Client starts up much faster. That was possible by modifing the blkindex.dat file structure. That means that when you update, you will have to delete the blkindex.dat and blk0001.dat files and re-download the entire block chain again.

More rpc commands added: getrawtransaction, getpeerinfo, listburnminted.

I have not yet fixed the PoS 100% CPU usage that some may have experienced. It seems to be an issue in the basis of PoS and not Slimcoin's additions. What I could do to "patch" this issue is disable PoS minting from startup and make the user add an option like -enable-pos-minting (or something) to make the client do PoS minting. The benefits of that are that staked coins will accumulate age and then, manually, the user could restart the client with that option. Since the coins have aged a lot, they will find the PoS blocks quickly, and then the user could restart the wallet w/o that option again. I want to reiterate that the main idea and innovation of Slimcoin was Proof of Burn. Proof of Stake should be considered an optional/extra part of Slimcoin.

One way that PoS issue can be resolved is by sending one big transaction with all of your coins to yourself, another address you own. That will destroy all of the coin age of those coins, but that will not take up any CPU since (as can be read from some posts above), the client will only have to split one tx into two and not hundreds of small txs into even smaller ones.

Small Note: The changes listed above to Pow, PoB, PoS will take place after a specific timestamp, so updating the wallet will be required within a certain time frame.

That's a good one I think, I vote for the option to enable/disable POS!!!!