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

[zahzin]

de.ckpool.org working for others ?

Seems I cannot connect to de pool, it and kano.is pool shows as dead to me, even though I can ping them, was able to mine on them fine until about a day ago when they started showing as dead on my s2. Hashes fine on solo.ckpool.org and other pools though.

Any reason why I would be blacklisted on de solo pool and kano.is, you guys have put in some new ddos protection perhaps? I am only mining, not ddossing

Screenshot from my S2, showing de and kano as dead but hashing ok on solo.
https://i.imgur.com/iZW9HZ7.jpg

Lol I even took it apart to pieces and vacuumed and cleaned it and reimaged SD card for two days until I found out S2 does not display hash boards or fan rpm or temps if all pools in the list are dead...

[firetreeactual]

de.ckpool.org working for others ?

Seems I cannot connect to de pool, it and kano.is pool shows as dead to me, even though I can ping them, was able to mine on them fine until about a day ago when they started showing as dead on my s2. Hashes fine on solo.ckpool.org and other pools though.

Any reason why I would be blacklisted on de solo pool and kano.is, you guys have put in some new ddos protection perhaps? I am only mining, not ddossing

Screenshot from my S2, showing de and kano as dead but hashing ok on solo.


Lol I even took it apart to pieces and vacuumed and cleaned it and reimaged SD card for two days until I found out S2 does not display hash boards or fan rpm or temps if all pools in the list are dead...

Just checked on Doc (my S2) and it's alive on the US and DE servers...on port 3333...and has been stable for over 60 hours now. I've found a couple of little things that are different with the S2 than the S3s I run...if you change the config, you have to do a hard boot to really get it to "take" sometimes. I found this out via a momentary power outage here (I don't run UPS); all the S3s (OK...so I like a little whackyness once in a while...they're named Sleepy, Dopey, Sneezy, and Grumpy) came back up and connected on their own. I had to power down the S2 on that instance to get it to engage; the same thing occurs if I change a pool assignment on occasion. Dunno why the inconsistency. The machine checks out OK.

Imua. 

[zahzin]

if you change the config, you have to do a hard boot to really get it to "take" sometimes. I found this out via a momentary power outage here (I don't run UPS); all the S3s (OK...so I like a little whackyness once in a while...they're named Sleepy, Dopey, Sneezy, and Grumpy) came back up and connected on their own. I had to power down the S2 on that instance to get it to engage; the same thing occurs if I change a pool assignment on occasion. Dunno why the inconsistency. The machine checks out OK.

Imua.  

I have been doing several "cold boots", even left it powerless for half and hour, and yesterday night when I had not figured the issue was with all pools being "dead" to me, (I had kano.is twice and once de.ckpool) thought my miner was dead since on S2 if all pools are dead it does not show hashing boards or temps(I did not know this at the time) so I thought it had really died and left it powered off without power cord for the night..

Only today found out that other pools were working ok, even the solo original pool and there was nothing wrong with S2 itself, just that I de.ckpool and kano.is are dead to me for some reason.. Was able to hash on them fine before yesterday though...

[itsnogood]

I tried a reboot but my 2 solo miners (S1 & S3) are showing de.ckpool port 3333 as dead. I changed to 3334 and that shows alive.

Both miners failed over to kano's pool and are working just fine for me.

[zahzin]

I tried a reboot but my 2 solo miners (S1 & S3) are showing de.ckpool port 3333 as dead. I changed to 3334 and that shows alive.

Both miners failed over to kano's pool and are working just fine for me.

Hmm seem to have a similar problem then, DE is now working for me as well once I tried 3334 port, 3333 was dead to me too..

As for failing to Kanos pool, that one is dead to my S2 no matter if I use my created username or bitcoin address to mine..

EDIT: Seems port 3333 at DE pool just started working for me.. Still got kanos pool dead though

EDIT2: Spoke too soon, 3333 port on DE not working for me anymore, failed over to 3334..

[Indianacoin]

I have been mining on F2Pool (at PPS mode) for quite a long time now. I just wanted to try out my luck at -ck's pool because I'm feeling lucky after this New Year

But I have a query regarding solo mining since I have no experience at all.

1. Do I need to keep my miners running 24*7 ?

2. What will happen if I stop mining for sometime in order to give a break?

3. How can I calculate my chance from the submitted shares every 5 minutes?

4. If a block is found by someone else, will I receive a fractional share from it or nothing?

6. Is merged mining other SHA-256 coins possible?

more nooby questions coming!

[firetreeactual]

I have been mining on F2Pool (at PPS mode) for quite a long time now. I just wanted to try out my luck at -ck's pool because I'm feeling lucky after this New Year

But I have a query regarding solo mining since I have no experience at all.

1. Do I need to keep my miners running 24*7 ?

2. What will happen if I stop mining for sometime in order to give a break?

3. How can I calculate my chance from the submitted shares every 5 minutes?

4. If a block is found by someone else, will I receive a fractional share from it or nothing?

6. Is merged mining other SHA-256 coins possible?

more nooby questions coming!

I'm not the expert here, but I can answer these. (1) Of course. If you're not mining, you're not mining...; (2) you won't find anything; refer to answer no. 1; (3) Why?; (4) This is a pool, but it is strictly solo mining. You only get paid if YOU find the block, and; (6) Nope. BTC only.

Actually, the solo.ckpool.org site gives answers as well.

I'm sensing that you have (like me) spent a fair amount of time on Slush's Pool, which is a great resource for newer folks as its dashboard and frontend are very user-friendly and provide good stats for the payout system they use. It's my failover at the present. In Slush, your scoring hash rate is somehow tied to how consistent ("loyal") you are, ie., how much time you're spending connected and mining...I run about 2Th/s at the moment, and it takes sometimes 2-3 hours to achieve "normal" scoring hash rate after being down for any length of time at all.

Kano's pool ROI is different; you get paid your comparative share, but it is not held in abeyance for some sort of threshold. It's sent manually as soon as the required confirmations are complete. Again, he's got a good explanation on it at www.kano.is (ie., ckpool). When I finish my self-imposed solo mining expedition on the 8th, I'll be going to Kano I believe.

Dunno if that's helpful.

Oh...short postscript...I never waste energy actually computing "chance." You're either lucky, or you're not... 

[-ck]

de pool front end needed a kick in the arse. Miners already connected to it were still mining fine. I haven't finished provisioning the solo server yet.

[philipma1957]

I have been mining on F2Pool (at PPS mode) for quite a long time now. I just wanted to try out my luck at -ck's pool because I'm feeling lucky after this New Year

But I have a query regarding solo mining since I have no experience at all.

1. Do I need to keep my miners running 24*7 ?

2. What will happen if I stop mining for sometime in order to give a break?

3. How can I calculate my chance from the submitted shares every 5 minutes?

4. If a block is found by someone else, will I receive a fractional share from it or nothing?

6. Is merged mining other SHA-256 coins possible?

more nooby questions coming!

answer for 1+2  
power on = you can win  
power off = you can't win

answer for 3 is complex   so here is one way go to the bitcoinwisdom

https://bitcoinwisdom.com/bitcoin/difficulty  punch in your hash power and look at the daily number of btc earned say it is   5 th  which right now gives you 0.02421 btc in a day

so 25 btc divide by  0.02421 = 1032 to 1 to hit a block in a day  this is a close estimate not perfect.

4) This is all or nothing baby!

6) yes but we don't do it and won't do it.

[DanielRo]

de pool front end needed a kick in the arse. Miners already connected to it were still mining fine. I haven't finished provisioning the solo server yet.

I had also problems with new miners connecting to de server 3333. I was thinking that the DDoS has some ip from my internet provider so I switched to hk. hk 443 works fine for me, for testing only.

[hedgy73]

Why so few blocks lately? Has the recent difficulty increases really made this much difference?

I notice there's 935TH mining at the moment.

[-ck]

Why so few blocks lately? Has the recent difficulty increases really made this much difference?

I notice there's 935TH mining at the moment.

Because diff + luck

[hedgy73]

Why so few blocks lately? Has the recent difficulty increases really made this much difference?

I notice there's 935TH mining at the moment.

Because diff + luck

I know a gypsy, perhaps I should buy a lucky rock from her....

[hodedowe]

Why so few blocks lately? Has the recent difficulty increases really made this much difference?

I notice there's 935TH mining at the moment.

Because diff + luck

I know a gypsy, perhaps I should buy a lucky rock from her....

You'd be better off buying a lucky bitcoin from someone. At least then you'd have a bitcoin

[hedgy73]

[hodedowe]

(img)

Bwahahahaha!

[hodedowe]

So I already mentioned that I have never, but has anyone else here pulled anything close to a 100b share? This new diff is a heart-stopper.

[madmartyk]

I did right before Christmas...  bestever": 101319884876  With 50T

[kano]

Why so few blocks lately? Has the recent difficulty increases really made this much difference?

I notice there's 935TH mining at the moment.

Because diff + luck

I know a gypsy, perhaps I should buy a lucky rock from her....

You'd be better off buying a lucky bitcoin from someone. At least then you'd have a bitcoin

I don't think you realise how wise those words really are ...

[-ck]

Hi all

I was getting bored so I've decided to upgrade the main solo pool to a much power powerful dedicated server with integrated DDoS protection. At some stage in the near future you will all experience a redirect to the new server. There should be virtually no downtime and your share results should carry over.

Should we continue to use 3334 with rentals from MRR with the new server?

The new server has been provisioned, deployed and you have all seamlessly been moved to it. I doubt any of you would have noticed anything unless you were watching your cgminer console at the time. Rental services should once again work fine on the regular 3333 port, although 3334 will still work to save you the trouble of changing your configurations Should a ddos happen again in the future that fails to protect the main server, I will only deploy a front end redirector then. The only substantial difference now is the server has moved from LA to Dallas. DE will shortly be tweaked too so that all ports work unless it experiences a DDoS (though it's not getting a server upgrade).

EDIT: De done too