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

[aarons6]

sometimes you get a bad s3

i got one.

https://c1.staticflickr.com/1/509/19372544826_0fa41d8827_o.png
https://c1.staticflickr.com/1/498/19398712875_a2373b88fb_o.png

currently mining 3 s3s on solo for the 4th of july weekend..
http://solo.ckpool.org/users/1D1V2wvDg9hMjj7uFpHYW7Dk1yp3pvHrGs

How do you figure that's a "bad" S3?  Is it because your reported hash rate in your monitoring tool is 412GH/s when it should read 440GH/s based on your clock speed?

i guess its not bad, since it works.. lol.

its just slower then the other 2 i have. has more hwe% and the fans think they are spinning at 10,000+ rpm.

so i guess its just special.. like short buss special.

[jonnybravo0311]

Ahh... it's that window-licking kinda special.

I've never seen an S3 fan spooled up to 10k rpm before.  The hash rate is closer to what I'd expect if your clock speed was set to 206.25 than it being set at the default 218.75.  Your display isn't showing any "x" or "-" so it would appear that all of the chips are functioning.  I'd say go into your config and kick the clock down a notch to 212.5, save and apply then reboot the thing.  When it comes back up, check on it after a while... it should get hashing ~427GH/s at that clock speed.

And this discussion really should be moved into the s3 support thread instead of cluttering up ck's solo pool thread.  So... to try and bring it back on track...

Now that hotwired007 found a block with his S1s... it's time for me to find a block with my U2s!  Unfortunately, they've yet to find a share better than 410,090 since the last block... and 3.75M since I last updated cgminer and rebooted on 6/23.

[kano]

You can check the settings via the API - I added the full set of antminer run settings to stats/estats in my version.
If you have java installed on your computer, master cgminer includes API.class
in https://github.com/ckolivas/cgminer

 java API estats IPAddressOfS3

If you are on linux you can use java or ncat/netcat:
 echo '{"command":"estats"}' | ncat -4 IPAddressOfS3 4028
or
 echo '{"command":"estats"}' | netcat -4 IPAddressOfS3 4028

miner_count, asic_count, timeout, frequency, regdata, voltage

[hotwired007]

Now that hotwired007 found a block with his S1s... it's time for me to find a block with my U2s!  Unfortunately, they've yet to find a share better than 410,090 since the last block... and 3.75M since I last updated cgminer and rebooted on 6/23.

I'm mining with a U2 and 23 block erupters too - i'm hoping that these may one day hit a block too!

[727miner]

Congrats to 17UhZWXLyiHmPmAb4VdFweGWRYY52qjxwp!

[HerbPean]

Congrats to 17UhZWXLyiHmPmAb4VdFweGWRYY52qjxwp!

Congrats Cheeseater |

[-ck]

Congrats to 17UhZWXLyiHmPmAb4VdFweGWRYY52qjxwp!

Congrats Cheeseater |

{"hashrate1m": "108T", "hashrate5m": "108T", "hashrate1hr": "107T", "hashrate1d": "97.3T", "hashrate7d": "83.5T", "lastupdate": 1436155692, "workers": 102

Code:

[2015-07-06 03:18:18] Possible block solve diff 157557972968.761505 !
[2015-07-06 03:18:18] BLOCK ACCEPTED!
[2015-07-06 03:18:18] Solved and confirmed block 364037

[Mikestang]

Congrats to 17UhZWXLyiHmPmAb4VdFweGWRYY52qjxwp!

Congrats Cheeseater |

{"hashrate1m": "108T", "hashrate5m": "108T", "hashrate1hr": "107T", "hashrate1d": "97.3T", "hashrate7d": "83.5T", "lastupdate": 1436155692, "workers": 102

Code:

[2015-07-06 03:18:18] Possible block solve diff 157557972968.761505 !
[2015-07-06 03:18:18] BLOCK ACCEPTED!
[2015-07-06 03:18:18] Solved and confirmed block 364037

Went out to get dinner and came back to see my best shares had reset, but my blocks found still read 0.  Some day... in the mean time, congrats to the solver!

[mavericklm]

congratz!

looks like 4blocks have been found by this address?!

[-ck]

Will be restarting the pool shortly for some minor tweaks to cope with transaction floods currently occurring.

EDIT: Complete

[tutorialevideo]

Will be restarting the pool shortly for some minor tweaks to cope with transaction floods currently occurring.

EDIT: Complete

The pool section where whe can see all the power pointed to solo mining is not working anymore..

http://solo.ckpool.org/pool/

[-ck]

Will be restarting the pool shortly for some minor tweaks to cope with transaction floods currently occurring.

EDIT: Complete

The pool section where whe can see all the power pointed to solo mining is not working anymore..

http://solo.ckpool.org/pool/

Works fine on firefox as a refreshing page, otherwise you need the direct page
http://solo.ckpool.org/pool/pool.status

Remember that pool stats are totally meaningless for individual miners here though and the stats are really there for me.

[tutorialevideo]

Will be restarting the pool shortly for some minor tweaks to cope with transaction floods currently occurring.

EDIT: Complete

The pool section where whe can see all the power pointed to solo mining is not working anymore..

http://solo.ckpool.org/pool/

Works fine on firefox as a refreshing page, otherwise you need the direct page
http://solo.ckpool.org/pool/pool.status

Remember that pool stats are totally meaningless for individual miners here though and the stats are really there for me.

Yes i know just whant to see how much power is pointed to the pool

[amidaemon]

found a block 364695
{"hashrate1m": "317T", "workers": 217}
http://solo.ckpool.org/users/1fj3xKoMfmv955J5sqpVJEAZAAEk3mvEN

[-ck]

found a block 364695
{"hashrate1m": "317T", "workers": 217}
http://solo.ckpool.org/users/1fj3xKoMfmv955J5sqpVJEAZAAEk3mvEN

Code:

[2015-07-10 12:19:10] Possible block solve diff 110991060930.534348 !
[2015-07-10 12:19:11] BLOCK ACCEPTED!
[2015-07-10 12:19:11] Solved and confirmed block 364695

[g00dwin555]

 

{"hashrate1m": "350T", "hashrate5m": "329T", "hashrate1hr": "327T", "hashrate1d": "94.7T", "hashrate7d": "39.2T", "lastupdate": 1436534187, "workers": 217,

3 is a block found))

thanks Ckpool !!

[wlefever]

Congrats 1fj3xKoMfmv955J5sqpVJEAZAAEk3mvEN !

[-ck]

Just to let miners know, Kano and I worked on minimising the latency of bitcoind under the current flood of transactions and I'm happy to say that we've been able to deploy some of my custom modifications to this and kano ckpool which still guarantee maximum transaction processing (i.e. never a zero transaction block) while minimising the risk of stale work / orphans. Plus we are NOT using a transaction blacklist; all transactions are prioritised on their own merit as per bitcoind rules.

[amidaemon]

found a block 364822
{"hashrate1m": "144T", "workers": 125}
http://solo.ckpool.org/users/3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY

[-ck]

found a block 364822
{"hashrate1m": "144T", "workers": 125}
http://solo.ckpool.org/users/3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY

Code:

[2015-07-11 07:25:24] Possible block solve diff 77216354250.960800 !
[2015-07-11 07:25:24] BLOCK ACCEPTED!
[2015-07-11 07:25:24] Solved and confirmed block 364822

This also confirms that 3* multisig addresses work fine