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

sid7039

full member

Activity: 221

Merit: 100

Quote from: slimcoin on August 06, 2014, 06:37:41 AM

Slimcoin pool is not on the correct blockchain.
Their last block found does not match the hash on the block explorer, which is on the correct chain: http://www.blockexperts.com/slm

I will write to the admin of slimcoinpool regarding this.

THX!
Please post the information here when they will switch to the correct blockchain. Till this time I'm stopping mining at this pool Sad

slimcoin

full member

Activity: 182

Merit: 100

Slimcoin pool is not on the correct blockchain.
Their last block found does not match the hash on the block explorer, which is on the correct chain: http://www.blockexperts.com/slm

I will write to the admin of slimcoinpool regarding this.

sid7039

full member

Activity: 221

Merit: 100

I have question about slimcoinpool.com

My stats at slimcoinpool says:
paid: 156.xxx SLM
unconfirmed: 470.xxx SLM

But in my wallet I have only 24.xxxx SLM (and also 1.5SLM burned).
Wallet v0.3.2.0-2-g53d7c33-alpha fully synced.

Why slimcoinpool says 156.xxx SLM paid when less than 30 SLM have been paid?

watcher60

newbie

Activity: 1

Merit: 0

Can anyone who uses slimcoinpool.com advise if they have actually received any payouts. I am a slow miner( 2KH/s), however had approx 350 SLM mined, and the site showed that it had sent approx 300 slm however I never received the coins to my wallet, and the TXhash shown appear not to be know - this was a couple of days back now, (ref http://slimcoinpool.com/worker/ST8Ahgj8xvoQY38HsQvLVHpp8FfyDQSFzh)

My slimcoin wallet shows as fully synch'd with 34 connection so appears to be up to date.

I swapped over to last night to slm.blockquarry.com, and even though I have the below shown in my miner and 13,944 valid shares in the site apparently I have zero earnings.
[2014-08-06 10:03:19] accepted: 1795/1802 (99.61%), 2.15 khash/s (yay!!!)

I know things are a little bit rough and ready currently but can anyone advise if I just need wait or it does sound like something is wrong?

thanks

W60

Cheeto02

newbie

Activity: 8

Merit: 0

For anyone interested the Slimcoin pool at https://slm.blockquarry.com is back up and running. We appear to be in sync with the correct block chain at block 59904 which agrees with the block explorer.

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: slimcoin on August 05, 2014, 12:38:30 PM

It is always the quickest to sync using: "-connect=212.75.31.155:41684".

What's happened to the seed node built into the client, dnsseed.slimcoinpool.com? Does not resolve.

My client didn't find any peers until I forced a connect to 76.127.202.17 (mentioned earlier in this thread).

You may want to consider fixing/adding seed nodes so that new users do not need to fiddle with client configs.

slimcoin

full member

Activity: 182

Merit: 100

It is always the quickest to sync using: "-connect=212.75.31.155:41684".

primer-

legendary

Activity: 1092

Merit: 1000

Slimcoin is dead, dont waste your time people...

almightyruler

legendary

Activity: 2268

Merit: 1092

Just installed slimcoin for the first time. Heights are all over the place. Is this because of crazy forking, or is it just coincidental that the majority (all but 1?) of the peers my client has connected to are not synced?

Code:

        "height" : 15164,
        "height" : 15164,
        "height" : 15157,
        "height" : 15164,
        "height" : 42547,
        "height" : 10515,
        "height" : 35306,
        "height" : 16927,
        "height" : 35587,
        "height" : 58389,
        "height" : 25550,
        "height" : 7052,
        "height" : 42925,
        "height" : 17772,
        "height" : 15443,
        "height" : 15164,
        "height" : 11323,
        "height" : 43666,
        "height" : 16270,

I've been stuck at 58371 for 45 mins, so something funny is definitely going on.

edit: and about 2 mins after I post this msg it starts syncing again, now synced to block 59796 (30 seconds old)

edit2: watching the debug log I can see many peers seem to be stuck in the classic infinite loop where they request a set of blocks, decide they are invalid (since they're on a fork), but then request the same blocks again, over and over. I guess the massive variation in heights is due to forking.

GrinZ

legendary

Activity: 1572

Merit: 1002

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

TrippyPippy

member

Activity: 110

Merit: 10

Quote from: slimcoin on August 04, 2014, 02:27:59 PM

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

Great it worked !!

Thanks

Trippy

slimcoin

full member

Activity: 182

Merit: 100

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

TrippyPippy

member

Activity: 110

Merit: 10

Quote from: slimcoin on July 20, 2014, 10:32:50 AM

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

LIghtvelocityCoin

sr. member

Activity: 320

Merit: 250

Quote from: Golph on August 04, 2014, 08:18:00 AM

Is this profitable?

It was.

LIghtvelocityCoin

sr. member

Activity: 320

Merit: 250

Quote from: primer- on August 04, 2014, 08:24:40 AM

Quote from: Golph on August 04, 2014, 08:18:00 AM

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.

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: Golph on August 04, 2014, 08:18:00 AM

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

Golph

full member

Activity: 153

Merit: 100

Is this profitable?

NOjust

sr. member

Activity: 318

Merit: 250

Quote from: apesconcert on August 03, 2014, 06:11:09 AM

Quote from: primer- on July 31, 2014, 05:11:09 PM

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

I can confirm this update fixes the block propagation issue.

Really great news

more smooth, more stable.
great effort.

a123

member

Activity: 98

Merit: 10

Quote from: slimcoin on August 02, 2014, 02:48:37 PM

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.

apesconcert

member

Activity: 83

Merit: 10

Quote from: primer- on July 31, 2014, 05:11:09 PM

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

I can confirm this update fixes the block propagation issue.

Really great news

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