[ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer!

[chiguireitor]

Clarifying some things:

The CPU utilization spikes come from the fact that the Staking needs to sign the individual transactions it is using. So, for example, you have around 200 incoming transactions from a pool, and you stake coins from 150 transactions, that means the wallet needs to sign EACH of the 150 transactions twice, one for the new staked part and one for the change part. ECDSA signing is particularly hard on the CPU because of the math involved and the HUGE numbers it uses.

If you send one transaction to another wallet containing all the outputs from the 200 transactions, you're simplifying the spendables from 200 to 1, making it easier to stake because now your wallet only needs to sign twice, not 300 times. That's why primer- solved it by sending all the coins to another wallet.

Alas, i haven't experienced this problem because i burn it all.

[1715574904]

1715574904

[glop]

Yes, that is it.
But in that process, when does that happen?

Does it only happen when the coins are old enough, which is after the 1 week wait time, or when the coins can create a valid PoS block.

  I had a look into the code:

  The process is launch every block but the calculation and split is done after 1 week of coin age.

  The perf problem should be into the election test as it tests every coins, it multiply the delay and load.

  Now it is to find out were and why because it has to be really quick .......

 

[glop]

   Slimcoin,

       Have you any idea about the time/ressource it takes to turn one loop in

       Cwallet::CreateCoinStake  

  ( because when POS is active, it is run by almost any coins in the wallet until fKernelFound and if you have many coins it could have a significant impact )

                  

[primer-]

   Slimcoin,

       Have you any idea about the time it takes to turn the one loop in

       Cwallet::CreateCoinStake   

  ( because it is run by any coins in the wallet until fKernelFound and if you have many coins it could have a significant impact )

                   

Dev has no internets at home, we will have to wait for an answer until tomorrow

[slimcoin]

I implemented the getrawtransaction command and also made changes to the wallet to make it start up faster.
I will push the commit onto github, but not provide binaries.

I will give binaries when the big update comes along.

[chiguireitor]

I implemented the getrawtransaction command and also made changes to the wallet to make it start up faster.
I will push the commit onto github, but not provide binaries.

I will give binaries when the big update comes along.

Yay!!!! Will compile it tonite and add support to my IAPs system!!!

[sp00lin9]

I implemented the getrawtransaction command and also made changes to the wallet to make it start up faster.
I will push the commit onto github, but not provide binaries.

I will give binaries when the big update comes along.

Thank you!

[slimcoin]

New update with getrawtransaction is up on github, there are no binaries for this update.

Other added commands include: getpeerinfo and listburnminted (lists the blocks minted by PoB by your client)

The update also makes the client start up significantly faster, but that requires you to delete the blkindex.dat and blk0001.dat files. If you do not delete them, the client will error out saying the blkindex.dat is corrupted.

Here is a link to the github slimcoin: https://github.com/slimcoin/slimcoin

[chiguireitor]

New update with getrawtransaction is up on github, there are no binaries for this update.

Other added commands include: getpeerinfo and listburnminted (lists the blocks minted by PoB by your client)

The update also makes the client start up significantly faster, but that requires you to delete the blkindex.dat and blk0001.dat files. If you do not delete them, the client will error out saying the blkindex.dat is corrupted.

Here is a link to the github slimcoin: https://github.com/slimcoin/slimcoin

Hmmm... sendrawtransaction wasn't included? also there's a need for signrawtransaction... plz plz pretty plz

[idad01]

New update with getrawtransaction is up on github, there are no binaries for this update.

Other added commands include: getpeerinfo and listburnminted (lists the blocks minted by PoB by your client)

The update also makes the client start up significantly faster, but that requires you to delete the blkindex.dat and blk0001.dat files. If you do not delete them, the client will error out saying the blkindex.dat is corrupted.

Here is a link to the github slimcoin: https://github.com/slimcoin/slimcoin

No executable?

[TheRealSteve]

No executable?

5 posts up. 5 posts. 5.

I will push the commit onto github, but not provide binaries.

I will give binaries when the big update comes along.

[theprofileth]

Can someone send some SLM to my address below I am interested in how the proof of burn functions in practice and am considering investing in some if it works properly.

[AizenSou]

Can someone send some SLM to my address below I am interested in how the proof of burn functions in practice and am considering investing in some if it works properly.

Cheap Slimcoins to buy at bter . Even with 0.1 BTC you will get a lot of Slim.

[slimcoin]

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.

[glop]

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!!!!

[a123]

thanks for the changes, it looks substantial!

perhaps there's no need for a new enable-pos-minting flag, but just make it reservebalance true largenum by default? user can then unset reservebalance after they've consolidated their txns.

would also like to re-iterate request for implementation for signrawtransaction / sendrawtransaction eventually on your timeline. this would help make it easier to develop services for the slimcoin ecosystem.

recently i was thinking that slimcoin's nature of discouraging heavy mining in the long run may also make the coin succumb more easily to 51% double-spend attacks. since PoB blocks can only tack on to an existing PoW block, PoB cannot itself form an alternate correct chain. a legitimate PoS and PoW/PoB combined chain however would likely orphan the malicious chain.

PoS would thus still be an integral part of maintaining the blockchain integrity and not just an optional/extra sideshow? Not sure if my understanding of the matter is right.

[idad01]

"difficulty" : 0.36893898,

Some people use the GPU SOLO?

slimcoinpool.com=634.349 KH/s
slm.blockquarry.com=155.825 KH/s

How will such a high difficulty？？

[a123]

the difficulty has been this high before due to PoS blocks. but the network hash rate of 9mh seems to be a all-time high.

[Vilchaco]

the difficulty has been this high before due to PoS blocks. but the network hash rate of 9mh seems to be a all-time high.

My coins are in my wallet since 1 week and 4 days ago... and still no stake... how to fix this?

[slimcoin]

Slimcoin now has a blockchain explorer at http://www.blockexperts.com/slm!