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

[primer-]

I guess i spoke too fast, my three wallets on three different networks went out of sync four times, for at least 15 minutes each time, in the last 8 hours.......

EDIT: Burned coins should be transferable. I want to sell off my 19k burned coins and rm -rf slimcoin forever..

[1715623441]

1715623441

[1715623441]

1715623441

[AizenSou]

I guess i spoke too fast, my three wallets on three different networks went out of sync four times, for at least 15 minutes each time, in the last 8 hours.......

EDIT: Burned coins should be transferable. I want to sell off my 19k burned coins and rm -rf slimcoin forever..

How could burned money be resold ? 
As long as primer- doesn't left, the coin will never die LOL

[gjhiggins]

EDIT: Burned coins should be transferable. I want to sell off my 19k burned coins and rm -rf slimcoin forever..

How could burned money be resold ? 

Export the privkey, sell that? Or am I missing something?


Cheers

Graham

[primer-]

EDIT: Burned coins should be transferable. I want to sell off my 19k burned coins and rm -rf slimcoin forever..

How could burned money be resold ? 

Export the privkey, sell that? Or am I missing something?


Cheers

Graham

Who is going to buy a priv key that I hold a copy of ?

[AizenSou]

EDIT: Burned coins should be transferable. I want to sell off my 19k burned coins and rm -rf slimcoin forever..

How could burned money be resold ? 

Export the privkey, sell that? Or am I missing something?


Cheers

Graham

That should be possible with crypto only LOL.

[a123]

So I turned off the auto SLM sending function and just exported the time stamps the blocks stopped syncing.

Aug 1 0730: 55674 - 55680: 8 minutes
Aug 1 0840: 55717 - 55720: 4 minutes
Aug 1 1115: 55849 - 55865: 20 minutes
Aug 1 1201: 55877 - 55893: 22 minutes
Aug 1 1502: 56020 - 56031: 16 minutes
Aug 1 1642: 56082 - 56097: 22 minutes
Aug 1 1748: 56135 - 56158: 26 minutes (Debug log sliced out for this section: http://pastebin.com/ytuNWsj9, btw 2 wallet flushes timestamped)
Aug 1 1930: 56215 - 56240: 21 minutes
Aug 1 2051: 56302 - 56323: 22 minutes
Aug 2 0140: 56538 - 56542: 4 minutes

For sharing. I'll try to figure out what's wrong as well hmm.

[slimcoin]

Has anyone felt any difference in the PoS cpu usage issue in the last update?

[m5j0r]

I'm not getting any mints. Burned about 1k SLM.
What is going on?

[hankrules]

I'm not getting any mints. Burned about 1k SLM.
What is going on?

From getburndata:         "Formatted nEffectiveBurnCoins" : "194604.713891"
That gives you a 0.00513862167059380566749644521847 chance of hitting a block each generation. It'll just take time.

[apesconcert]

New Update

TL;DR: The client will now use less cpu resources and the blocks will propagate faster.

I looked around the source code to see where the PoS was using so much CPU usage. I finally found it today, it was actually an issue with how the PoS used the block.GetHash() function so freely. I forked this off of Peercoin, so the GetHash() used double SHA256, not that intense. Dcrypt is much, much more intensive, yet it was called in the same places. I made changes that removed the need to call GetHash() at all on PoS. I ran an absolute worse case test and it used 50% of 1 core. On normal usage, PoS used 8-10% on 1 core, compared to the 3-5% on 1 core with PoS disabled. I even looked further into making PoS use less cpu, the portion that adds the 5% cpu usage to the client is part of the core of PoS, and cannot be optimized. I searched for other places in the client that could suffer from a similar issue of excessive calls of GetHash(). I found 2 more in the "getdata" command and the "block" command the nodes send to each other.

Downloads
 - Source code: https://github.com/slimcoin/slimcoin
 - Binaries (Linux and windows): cutable

I can confirm this update fixes the block propagation issue.

Really great news

[a123]

Has anyone felt any difference in the PoS cpu usage issue in the last update?

I was running a client cpu-bound to a single G1620 for PoS both before and after, and cpu utilisation appears to drop from about 25ish to 15ish. But it's hard to say as I wasn't monitoring the utilisation in particular.

[NOjust]

New Update

TL;DR: The client will now use less cpu resources and the blocks will propagate faster.

I looked around the source code to see where the PoS was using so much CPU usage. I finally found it today, it was actually an issue with how the PoS used the block.GetHash() function so freely. I forked this off of Peercoin, so the GetHash() used double SHA256, not that intense. Dcrypt is much, much more intensive, yet it was called in the same places. I made changes that removed the need to call GetHash() at all on PoS. I ran an absolute worse case test and it used 50% of 1 core. On normal usage, PoS used 8-10% on 1 core, compared to the 3-5% on 1 core with PoS disabled. I even looked further into making PoS use less cpu, the portion that adds the 5% cpu usage to the client is part of the core of PoS, and cannot be optimized. I searched for other places in the client that could suffer from a similar issue of excessive calls of GetHash(). I found 2 more in the "getdata" command and the "block" command the nodes send to each other.

Downloads
 - Source code: https://github.com/slimcoin/slimcoin
 - Binaries (Linux and windows): cutable

I can confirm this update fixes the block propagation issue.

Really great news

more smooth, more  stable.
great effort.

[Golph]

Is this profitable?

[primer-]

Is this profitable?

No, at the moment it is broken (keeping in sync with the network is impossible) and completely unprofitable. Waste of time.

Still looking to sell 19k burned SLM...

[LIghtvelocityCoin]

Is this profitable?

No, at the moment it is broken (keeping in sync with the network is impossible) and completely unprofitable. Waste of time.

Still looking to sell 19k burned SLM...

imagine that the initial price when it was on Bter.

[LIghtvelocityCoin]

Is this profitable?

It was. 

[TrippyPippy]

If you cannot sync, try using -connect=212.75.31.155:41684 instead. Also make sure you deleted you blkindex.dat, blk0001.dat, and addr.dat files.

Hi,

Where do I put the "-connect=212.75.31.155:41684" ?

In the slm.conf file exactly as it is ?

Trippy

[slimcoin]

Put the following in your slimcoin.conf file "addnode=76.127.202.17" exactly as it is.

[TrippyPippy]

Put the following in your slimcoin.conf file "addnode=76.127.202.17" exactly as it is.

Great it worked !!

Thanks

Trippy

[GrinZ]

MultiFaucet.tk
We provide SLM BlockExplorer and Faucet.
Join us!