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

hankrules

hero member

Activity: 673

Merit: 500

Quote from: m5j0r on August 03, 2014, 04:11:15 AM

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.

m5j0r

full member

Activity: 140

Merit: 100

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

slimcoin

full member

Activity: 182

Merit: 100

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

a123

member

Activity: 98

Merit: 10

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.

AizenSou

hero member

Activity: 938

Merit: 1000

Quote from: gjhiggins on August 01, 2014, 08:32:14 AM

Quote from: AizenSou on August 01, 2014, 08:10:53 AM

Quote from: primer- on August 01, 2014, 06:45:10 AM

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 ? Grin

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

Cheers

Graham

That should be possible with crypto only LOL.

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: gjhiggins on August 01, 2014, 08:32:14 AM

Quote from: AizenSou on August 01, 2014, 08:10:53 AM

Quote from: primer- on August 01, 2014, 06:45:10 AM

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 ? Grin

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 ?

gjhiggins

legendary

Activity: 2254

Merit: 1290

Quote from: AizenSou on August 01, 2014, 08:10:53 AM

Quote from: primer- on August 01, 2014, 06:45:10 AM

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 ? Grin

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

Cheers

Graham

AizenSou

hero member

Activity: 938

Merit: 1000

Quote from: primer- on August 01, 2014, 06:45:10 AM

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 ? Grin

As long as primer- doesn't left, the coin will never die LOL

primer-

legendary

Activity: 1092

Merit: 1000

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

a123

member

Activity: 98

Merit: 10

Quote from: slimcoin on July 31, 2014, 10:51:12 AM

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

Thanks for the fix! It definitely wasn't an easy task to root out the problem. Downloading and testing it now.

(edit)
Incidentally, I had much difficulties downloading the blockchain despite the -maxconnection settings; but once I commented out all addnode= entries in the slimcoin.conf file everything went smoothly.
(/edit)

a123

member

Activity: 98

Merit: 10

Quote from: idad01 on August 01, 2014, 04:35:07 AM

Quote from: AizenSou on August 01, 2014, 04:31:58 AM

Code:

"difficulty" : 0.99092765,
    "errors" : "",
    "generate" : false,
    "genproclimit" : -1,
    "hashespersec" : 0,
    "networkghps" : 0.01028020,

It is real?? Huh

Yes, POS mechanism clearly a problem!

PoS cpu-hogging is just fixed, so I presume there's a sudden release of txns ready for minting. There's also an upcoming PoS fix which should kick in on Aug 4 that reduces the PoS generation rate by 10x.

idad01

full member

Activity: 148

Merit: 100

Quote from: idad01 on August 01, 2014, 04:21:14 AM

55523-55573 block
pob=1
pow=7
pos=42

This is normal?

POS block occupies 85%

idad01

full member

Activity: 148

Merit: 100

Quote from: AizenSou on August 01, 2014, 04:31:58 AM

Code:

"difficulty" : 0.99092765,
    "errors" : "",
    "generate" : false,
    "genproclimit" : -1,
    "hashespersec" : 0,
    "networkghps" : 0.01028020,

It is real?? Huh

Yes, POS mechanism clearly a problem!

AizenSou

hero member

Activity: 938

Merit: 1000

Code:

"difficulty" : 0.99092765,
    "errors" : "",
    "generate" : false,
    "genproclimit" : -1,
    "hashespersec" : 0,
    "networkghps" : 0.01028020,

It is real?? Huh

idad01

full member

Activity: 148

Merit: 100

55523-55573 block
pob=1
pow=7
pos=42

This is normal?

hankrules

hero member

Activity: 673

Merit: 500

Quote from: halicarton on July 31, 2014, 09:35:18 PM

Is slimcoin SC? What about the price of SC now?

No, SC is silkcoin. Slimcoin is SLM. You can trade here: https://bter.com/trade/SLM_BTC

halicarton

sr. member

Activity: 402

Merit: 250

Is slimcoin SC? What about the price of SC now?

hankrules

hero member

Activity: 673

Merit: 500

Quote from: slimcoin on July 31, 2014, 10:51:12 AM

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): https://github.com/slimcoin/slimcoin-executable

Does this mean all known issues are resolved?

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: slimcoin on July 31, 2014, 10:51:12 AM

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): https://github.com/slimcoin/slimcoin-executable

I can confirm this update fixes the block propagation issue.

slimcoin

full member

Activity: 182

Merit: 100

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): https://github.com/slimcoin/slimcoin-executable

Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 38. (Read 284975 times)