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

[bgibso01]

Host provider seems to be having intermittent networking issues again, sorry - last time this happened one of the other servers on their subnet was experiencing a DDoS. Put in a support ticket but there's not much I can do about it at this time. If the pool was bigger I could probably justify moving to a more expensive provider with better connectivity guarantees.

No biggie here.  I think it's a great idea for a pool.  Beats me having to maintain my own solo side.  Although when things slow down at work, I plan to try setting up one of these.  From what I've seen so far with this and the other pool, it looks very good.  In the morning I'll point the S4 over to eligius and see what kind of rates I get there.  Thanks for what you are doing!

FYI: With the updated cgminer, the S4's gui doesn't report 5s hashrate.  Shows avg just fine though. Just in case you didn't know.

[dmwardjr]

k. Thanks for checking.  It's probably this instance of bfgminer I'm running

I see what you did there. Now that's funny right there 

Updated the S4 with your release today and pointed it at the solo pool.  I'm seeing an average of about 1.8t with it.  Does that sound about right?  Isn't it amazing we are up to a point where 200gh/s can be within 10% tolerance?

Specifications:
* Chip Operating Voltage: 0.72V

* Chip Quantity per unit: 160

* Hash Rate: 2,000GH/s guaranteed

* Power Efficiency: 0.69Watt/GH/s at the wall

* Over clocking: About 10%, but not guaranteed

* 3U Rack  432mm*442mm*133mm

* PSU inside: 1400W, 80PLUS gold, C14 input socket. Power line not included. You may look for one line with no less than 16A in your local market

* Temperature: 40-50 degree Celsius tested in the mining farm

* Fan Speed: 3900RPM

* Stable but a little bit noisy

* Ethernet connection, Stand alone

* Certificate Compliance: FCC/CE

I don't understand... The 10% tolerance regards "Over Clocking," which is "...not guaranteed."

However, a "Hash Rate: 2,000 GH/s (2 TH/s) is guaranteed."

[bgibso01]

Yes you are correct.  I was just thinking about how things have changed so quickly. ie. a 5gh/s tolerance was a big deal.

[dmwardjr]

Yes you are correct.  I was just thinking about how things have changed so quickly. ie. a 5gh/s tolerance was a big deal.

So, it was a "5 gh/s" shy of 2,000 GH/s or was it 200 GH/s shy ["1.8 TH/s average," like in your first statement.] shy of the 2 TH/s guarantee?

The reason I'm curious is because I'm about to purchase my first S4 in a couple more days.  I've almost mined the BTC needed to purchase it from Bitmaintech.com.

I'm just saying, I would be disappointed if it's not hashing the 2000 GH/s guaranteed.  I would need to send my S4 back if it was 200 GH/s shy of the 2000 GH/s guaranteed.  If it was just 5 GH/s shy of the 2000 GH/s, I could probably live with that; but not 200 GH/s shy of the guarantee.

[philipma1957]

Yes you are correct.  I was just thinking about how things have changed so quickly. ie. a 5gh/s tolerance was a big deal.

So, it was a "5 gh/s" shy of 2,000 GH/s or was it 200 GH/s shy ["1.8 TH/s average," like in your first statement.] shy of the 2 TH/s guarantee?

The reason I'm curious is because I'm about to purchase my first S4 in a couple more days.  I've almost mined the BTC needed to purchase it from Bitmaintech.com.

I'm just saying, I would be disappointed if it's not hashing the 2000 GH/s guaranteed.  I would need to send my S4 back if it was 200 GH/s shy of the 2000 GH/s guaranteed.  If it was just 5 GH/s shy of the 2000 GH/s, I could probably live with that; but not 200 GH/s shy of the guarantee.

no this was a pool issue.  my underclocked s-3 runs at 400-410gh.  the last two hours it has dropped out and back and is a mess.  but most of the time I get my 400-410gh here .  my s-3 is clocked to freq 200  so 400-410 is normal.

[dmwardjr]

Yes you are correct.  I was just thinking about how things have changed so quickly. ie. a 5gh/s tolerance was a big deal.

So, it was a "5 gh/s" shy of 2,000 GH/s or was it 200 GH/s shy ["1.8 TH/s average," like in your first statement.] shy of the 2 TH/s guarantee?

The reason I'm curious is because I'm about to purchase my first S4 in a couple more days.  I've almost mined the BTC needed to purchase it from Bitmaintech.com.

I'm just saying, I would be disappointed if it's not hashing the 2000 GH/s guaranteed.  I would need to send my S4 back if it was 200 GH/s shy of the 2000 GH/s guaranteed.  If it was just 5 GH/s shy of the 2000 GH/s, I could probably live with that; but not 200 GH/s shy of the guarantee.

no this was a pool issue.  my underclocked s-3 runs at 400-410gh.  the last two hours it has dropped out and back and is a mess.  but most of the time I get my 400-410gh here .  my s-3 is clocked to freq 200  so 400-410 is normal.

gotcha!

Thanks for clarifying!!!

I was beginning to get very concerned.

[-ck]

I've recruited a new server to cover this outage as it seems the hoster still hasn't weathered the storm of the DDoS.

EDIT:  No need to use this any more, I migrated the server somewhere more stable. Don't change anything.

Point your clients at:
solo2.ckpool.org:3334

Same login conditions etc. Unfortunately there are no stats pages set up, but consider this temporary till the DDoS is over. I have this pool starting at diff1 too since so many clients have slow devices mining here, but it ramps up very quickly if you have a faster device so don't worry (or you can add --suggest-diff if you're using the latest cgminer if you really want to force the issue).

[Rabinovitch]

Point your clients at:
solo2.ckpool.org:3334

Is this change permanent?

[-ck]

Point your clients at:
solo2.ckpool.org:3334

Is this change permanent?

No, but I'm having serious reservations about the existing VPS provider and may move the original ckpool to this other provider, though it costs me literally 10x as much to run compared to the first... but then it's probably 10x better.

[-ck]

VPS issues have been resolved, thanks for your patience. I'll leave the other node at solo2.ckpool.org there since some of you have started using it and I already hate how much I've interrupted your mining today it is a more powerful server). I may just migrate everything there long term. If I do migrate you won't need to do anything as I'll reassign the solo.ckpool.org name there.

EDIT: It seems the stability of solo 1 was short lived, will proceed with migration ASAP.

[-ck]

Server migration to beefier VPS complete. This one should be much more stable though it costs me 10x more to run (as always, you get what you pay for ).

You will not need to do anything, your DNS will pick up the new solo.ckpool.org IP address and your miners will switch to it whenever they reconnect. The only thing you may notice is your stats will be reset. Those who switched to solo2 are on the same server already, it points to the same address, and port 3334 on that one is the new tube pool. When I can see no one mining on the old server I will shut it down.

Good luck with your solo mining!

[yxt]

... I've set up extra solo pool nodes so the same conditions as the solo.ckpool.org (ie solo mine to your bitcoin address)

First runs diff of 2048:
s4.ckpool.org:3333

Second starts at diff 1 like ghash would:
s4.ckpool.org:3334

Bear in mind that ckpool adjusts diff VERY quickly so it may still work okay.

Are there still S4 nodes?

[-ck]

Are there still S4 nodes?

No, they were just for testing. S4s work fine on the regular solo pool, and even better with the new binary I put up.

[yxt]

Are there still S4 nodes?

No, they were just for testing. S4s work fine on the regular solo pool, and even better with the new binary I put up.

can't confirm this.

with cgminer 4.6.1 (shipped so from bitmaintech)
after ~20min I have a unit ~45Gh/s and Diff 3

{"hashrate1m": "774G", "hashrate5m": "461G", "hashrate1hr": "143G", "hashrate1d": "72.3G", "hashrate7d": "898M", "workers": 4}

stat is working? should be 5 workers


EDIT: 1838 GH/s and diff 97 now

[-ck]

Are there still S4 nodes?

No, they were just for testing. S4s work fine on the regular solo pool, and even better with the new binary I put up.

can't confirm this.

with cgminer 4.6.1 (shipped so from bitmaintech)
after ~20min I have a unit ~45Gh/s and Diff 3

{"hashrate1m": "774G", "hashrate5m": "461G", "hashrate1hr": "143G", "hashrate1d": "72.3G", "hashrate7d": "898M", "workers": 4}

stat is working? should be 5 workers


EDIT: 1838 GH/s and diff 97 now

The standard binary is pretty flaky which is why I put up a fixed one, though most people confirmed it does eventually work on ckpools. I'll restart the node at the default starting diff of 1024 it used to have on the old node. It seems that alleviates the pain of the start dodginess the S4s might have.

[yxt]

{"hashrate1m": "7.75T", "hashrate5m": "7.04T", "hashrate1hr": "6.83T", "hashrate1d": "6.81T", "hashrate7d": "25G", "workers": 4}

much better 
But still one missing worker

[-ck]

{"hashrate1m": "7.75T", "hashrate5m": "7.04T", "hashrate1hr": "6.83T", "hashrate1d": "6.81T", "hashrate7d": "25G", "workers": 4}

much better 
But still one missing worker

You'll still get an even better hashrate if you update the binary as I outlined on the S4 thread.

If it says 4, that means only 4 workers are submitting hashes. Presumably if you have 5 then one of them is not producing shares at all so it needs attention.

[Bakal]

Hi Ck...

so i point my miners to:

solo.ckpool.org:3333 or 3334?

thank you thank you

[wttbs]

Hi Ck...

so i point my miners to:

solo.ckpool.org:3333 or 3334?

thank you thank you

solo.ckpool.org:3333 is the right one

[Bakal]

thank you