[∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved!

[yslyung]

now we flying high !

time for a block ! c'mon CK do your magic . . .

{"hashrate1m": "471T", "hashrate5m": "368T", "hashrate1hr": "119T", "hashrate1d": "87.5T", "hashrate7d": "547G", "workers": 21}

[1713413075]

1713413075

[1713413075]

1713413075

[1713413075]

1713413075

[1713413075]

1713413075

[-ck]

now we flying high !

time for a block ! c'mon CK do your magic . . .

{"hashrate1m": "471T", "hashrate5m": "368T", "hashrate1hr": "119T", "hashrate1d": "87.5T", "hashrate7d": "547G", "workers": 21}

Okay now you're talking! You managed to push the ckpool CPU usage up past 1%! It periodically gets to 1.3%! Good work. Now find a block.

[yslyung]

now we flying high !

time for a block ! c'mon CK do your magic . . .

{"hashrate1m": "471T", "hashrate5m": "368T", "hashrate1hr": "119T", "hashrate1d": "87.5T", "hashrate7d": "547G", "workers": 21}

Okay now you're talking! You managed to push the ckpool CPU usage up past 1%! It periodically gets to 1.3%! Good work. Now find a block.

{"hashrate1m": "529T", "hashrate5m": "450T", "hashrate1hr": "156T", "hashrate1d": "113T", "hashrate7d": "750G", "workers": 21}

a little more yeah i feel it coming !

[nreal]

S3:s cant handle this much stress theyre given from ckpool, they keep rebooting every now and then. Newer has it happened when mined on p2pool, or i havent noticed that. 3 of 4 have crashed in 13 hours..

Ive installed this cgminer to all of them http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer

[yslyung]

S3:s cant handle this much stress theyre given from ckpool, they keep rebooting every now and then. Newer has it happened when mined on p2pool, or i havent noticed that. 3 of 4 have crashed in 13 hours..

Ive installed this cgminer to all of them http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer

my s3's are fine, no problems hashing away. maybe you wanna try the 3334 port ?

mine are running stock FW from BM. so far so good here.

[nreal]

S3:s cant handle this much stress theyre given from ckpool, they keep rebooting every now and then. Newer has it happened when mined on p2pool, or i havent noticed that. 3 of 4 have crashed in 13 hours..

Ive installed this cgminer to all of them http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer

my s3's are fine, no problems hashing away. maybe you wanna try the 3334 port ?

mine are running stock FW from BM. so far so good here.

Same reboot happened when tried to solomine terracoin, cant remember if it was stock FW then on s3s.
S1 ones rebooted also when tried to solo terracoin, they seem to be stable on ckpool.

Theyre all hashing at +6C temperature so overheating is not possible I think.

[wasikidding]

S3:s cant handle this much stress theyre given from ckpool, they keep rebooting every now and then. Newer has it happened when mined on p2pool, or i havent noticed that. 3 of 4 have crashed in 13 hours..

Ive installed this cgminer to all of them http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer

my s3's are fine, no problems hashing away. maybe you wanna try the 3334 port ?

mine are running stock FW from BM. so far so good here.

Same reboot happened when tried to solomine terracoin, cant remember if it was stock FW then on s3s.
S1 ones rebooted also when tried to solo terracoin, they seem to be stable on ckpool.

Theyre all hashing at +6C temperature so overheating is not possible I think.

6c seems really low most hash 250m at like 48-50c are your sensors bad

[nreal]

S3:s cant handle this much stress theyre given from ckpool, they keep rebooting every now and then. Newer has it happened when mined on p2pool, or i havent noticed that. 3 of 4 have crashed in 13 hours..

Ive installed this cgminer to all of them http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer

my s3's are fine, no problems hashing away. maybe you wanna try the 3334 port ?

mine are running stock FW from BM. so far so good here.

Same reboot happened when tried to solomine terracoin, cant remember if it was stock FW then on s3s.
S1 ones rebooted also when tried to solo terracoin, they seem to be stable on ckpool.

Theyre all hashing at +6C temperature so overheating is not possible I think.

6c seems really low most hash 250m at like 48-50c are your sensors bad

Room temperature is +6C

[-ck]

S3:s cant handle this much stress theyre given from ckpool, they keep rebooting every now and then. Newer has it happened when mined on p2pool, or i havent noticed that. 3 of 4 have crashed in 13 hours..

Ive installed this cgminer to all of them http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer

The workload keeps dropping down at regular intervals when you're on p2pool. On ckpool your s3 will be working its arse off all the time, meaning if you are running it at some kind of overclock, you may need to cut back a bit.

[nreal]

S3:s cant handle this much stress theyre given from ckpool, they keep rebooting every now and then. Newer has it happened when mined on p2pool, or i havent noticed that. 3 of 4 have crashed in 13 hours..

Ive installed this cgminer to all of them http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer

The workload keeps dropping down at regular intervals when you're on p2pool. On ckpool your s3 will be working its arse off all the time, meaning if you are running it at some kind of overclock, you may need to cut back a bit.

Might be the load, or s3s dont like when stratum connection is interrupted - switching from ckpool to p2pool and back. That happens here, Ill install local ckpool and set that as first backup. S3:s got some bug maybe with stats because those wont display best share with all miner settings on p2pool.
With share diff 1024 best share doesnt show, diff 500 it does..
It doesnt matter here that stats are reseted if it still goes on and finds a block

[yslyung]

http://solo.ckpool.org/tube/users/1LnGSCuCkMEsTjFw6UgMLoqkMicHxjdCYR

BLOCK !!!!!!!!































just messing around . . .






looks like no luck on lucky draw











waiting . . .

[-ck]

http://solo.ckpool.org/tube/users/1LnGSCuCkMEsTjFw6UgMLoqkMicHxjdCYR

BLOCK !!!!!!!!

Now you're a naughty boy  I was looking at my logs trying to figure out why it wasn't showing up at the pool lol.

[-ck]

We concluded some S4 testing in the last 24 hours and confirmed they work perfectly fine on this pool. While it may be a conflict of my own interests, I've helped the bitmain team so that they can modify the devices to work better on all pools.

[daddyfatsax]

Whoa... My worker count just doubled and my hash rate tanked. Doing any pool work ck?

[-ck]

Whoa... My worker count just doubled and my hash rate tanked. Doing any pool work ck?

Nope, didn't touch anything. I checked the logs and only your clients were misbehaving. They all seemed to reconnect over a 2 minute timeframe. The worker count can take a while to go down if you hadn't disconnected cleanly and the old instances are still in ckpool's recent memory.

[daddyfatsax]

Whoa... My worker count just doubled and my hash rate tanked. Doing any pool work ck?

Nope, didn't touch anything. I checked the logs and only your clients were misbehaving. They all seemed to reconnect over a 2 minute timeframe. The worker count can take a while to go down if you hadn't disconnected cleanly and the old instances are still in ckpool's recent memory.

Lovely. Thanks for the heads up.

Edit: Yep it was me. All my Ants and 1 jupiter jumped to my backup pool. Weird thing is they are in different locations.

[ImogenV]

And others say they don't work on Guild...I love how it seems ASICs are becoming even less consistent than their first generation units.

Occasionally they ping us after the fact and expect us to fix their problems.

...which is exactly what happened with the S4...

It turns out the controller is so low powered that it can only process ~30 shares per second which mean that unless diff is set higher, they work their way into a death spiral before diff catches up. Great...

(quoted from another thread)


Is this a problem if one is using an S4 with solo.ckpool.org?

[-ck]

It turns out the controller is so low powered that it can only process ~30 shares per second which mean that unless diff is set higher, they work their way into a death spiral before diff catches up. Great...

(quoted from another thread)


Is this a problem if one is using an S4 with solo.ckpool.org?

No. S4s work fine here.

[dmwardjr]

It turns out the controller is so low powered that it can only process ~30 shares per second which mean that unless diff is set higher, they work their way into a death spiral before diff catches up. Great...

(quoted from another thread)


Is this a problem if one is using an S4 with solo.ckpool.org?

No. S4s work fine here.

As you know, if you monitor, I move my S3's (4.7 TH/s) here on Saturday and/or Sunday after we find at least 5 blocks on Slush.  I had them hooked up this past Sunday for approximately 5 to 6 hours.  Your pool connectivity works great with my S3's.  I intend to choose either Saturday or Sunday to let them mine THE ENTIRE 24 hours after I get more miners in.

I believe you also know I've mentioned getting nothing but S4's from here on out when I buy more miners.  However, you have me a little concerned about them.  It sounds like they work fine on your pool.  Did you have the opportunity to test them on Slush and see if they performed properly?  I would rather use Bitmain BUT I do not want to be pissed off at Bitmain if they do not work on Slush as well as here.  Am I safe getting them?

Your reply is appreciated greatly.

[dmwardjr]

And others say they don't work on Guild...I love how it seems ASICs are becoming even less consistent than their first generation units.

Occasionally they ping us after the fact and expect us to fix their problems.

...which is exactly what happened with the S4...

It turns out the controller is so low powered that it can only process ~30 shares per second which mean that unless diff is set higher, they work their way into a death spiral before diff catches up. Great...

(quoted from another thread)


Is this a problem if one is using an S4 with solo.ckpool.org?

Since Slush has their Diff made to AUTOMATICALLY adjust, does this mean the S4 will be fine on Slush?