I don't monitor my miners too often, how do I know that I've hit a block?
Are there any alert system?
Thanks.
Topic: [∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved! - page 222. (Read 1514767 times)
February 10, 2016, 08:05:00 AM
February 10, 2016, 12:41:39 AM
I mean it isn't much. I have it at 0.05 per person for a buy-in, but hopefully the group can gain more blocks, popularity and investors to have people interested in the larger rentals
If you're interested: https://bitcointalksearch.org/topic/closedsolo-group-mining-block-breakers-united-1345538
For sure I am .. thank you - I'll be over to check it out.
February 10, 2016, 12:33:15 AM
Had approx 900TH for 18 hours and best I saw was ..
8656858836.6964016
Looks like > 1 PHs is the min now, for at least 2 days .. outta my price-risk-range - but I wonder if using port 3334 messed me in any way. The Germans, with not that much more hash than I had have 655117758757 .. 2 whole digits more .. sux
Ports shouldn't have given any problems. But nowadays it makes more sense to get in with a group to reduce your risk. Unless you can risk 10BTC and not mind losing it.
Aye .. learned my lesson.
We should all get together (25 people), on an ongoing basis. Each person puts in 0.5 every week, for a total of 12.5 BTC .. get 2.5 PHs for 20 hours. If we hit everyone doubles up. Or 0.25 x 25 for a total of 6.25 = 1PH for 24 hours .. call it CKDay .. limited risk, for a potential quadruple-up.
Maybe CK can do the escrow for us.
ezeminer already has a mining group just like that going, we had our first 24hr run completed yesterday with 150TH and got a 7B share, not the 144B that's currently needed, you should join in
If you're interested: https://bitcointalksearch.org/topic/closedsolo-group-mining-block-breakers-united-1345538
February 09, 2016, 11:52:34 PM
Had approx 900TH for 18 hours and best I saw was ..
8656858836.6964016
Looks like > 1 PHs is the min now, for at least 2 days .. outta my price-risk-range - but I wonder if using port 3334 messed me in any way. The Germans, with not that much more hash than I had have 655117758757 .. 2 whole digits more .. sux
Ports shouldn't have given any problems. But nowadays it makes more sense to get in with a group to reduce your risk. Unless you can risk 10BTC and not mind losing it.
Aye .. learned my lesson.
We should all get together (25 people), on an ongoing basis. Each person puts in 0.5 every week, for a total of 12.5 BTC .. get 2.5 PHs for 20 hours. If we hit everyone doubles up. Or 0.25 x 25 for a total of 6.25 = 1PH for 24 hours .. call it CKDay .. limited risk, for a potential quadruple-up.
Maybe CK can do the escrow for us.
ezeminer already has a mining group just like that going, we had our first 24hr run completed yesterday with 150TH and got a 7B share, not the 144B that's currently needed, you should join in
February 09, 2016, 11:25:04 PM
Had approx 900TH for 18 hours and best I saw was ..
8656858836.6964016
Looks like > 1 PHs is the min now, for at least 2 days .. outta my price-risk-range - but I wonder if using port 3334 messed me in any way. The Germans, with not that much more hash than I had have 655117758757 .. 2 whole digits more .. sux
Ports shouldn't have given any problems. But nowadays it makes more sense to get in with a group to reduce your risk. Unless you can risk 10BTC and not mind losing it.
Aye .. learned my lesson.
We should all get together (25 people), on an ongoing basis. Each person puts in 0.5 every week, for a total of 12.5 BTC .. get 2.5 PHs for 20 hours. If we hit everyone doubles up. Or 0.25 x 25 for a total of 6.25 = 1PH for 24 hours .. call it CKDay .. limited risk, for a potential quadruple-up.
Maybe CK can do the escrow for us.
February 09, 2016, 11:08:54 PM
Had approx 900TH for 18 hours and best I saw was ..
8656858836.6964016
Looks like > 1 PHs is the min now, for at least 2 days .. outta my price-risk-range - but I wonder if using port 3334 messed me in any way. The Germans, with not that much more hash than I had have 655117758757 .. 2 whole digits more .. sux
Ports shouldn't have given any problems. But nowadays it makes more sense to get in with a group to reduce your risk. Unless you can risk 10BTC and not mind losing it.
February 09, 2016, 10:29:53 PM
Had approx 900TH for 18 hours and best I saw was ..
8656858836.6964016
Looks like > 1 PHs is the min now, for at least 2 days .. outta my price-risk-range - but I wonder if using port 3334 messed me in any way. The Germans, with not that much more hash than I had have 655117758757 .. 2 whole digits more .. sux
February 09, 2016, 09:15:09 PM
1. would this be a good alternative to the previously setup SG remote solo node awhile back?
2. if yes, could you check if my BTC address is sending hash to US node correctly as if the S5 was located in US?
1. I'm sure it will be fine.2. if yes, could you check if my BTC address is sending hash to US node correctly as if the S5 was located in US?
2. You can see for yourself to see if the hashrate matches the expected. In short I can see no reason why it would be a problem no matter how far away the node is.
February 09, 2016, 09:04:24 PM
Hi CK,
I was playing with my lone s5 to be rented out at MRR.
In Antminer pool settings, will be set to MRR servers, one of them was an Asian node which gave me good ping, around 40ms.
During the setup, I could put it to mine to pools when it was not rented.
Currently pool setup at MRR is set to US solo ckpool node with kano US failover, and seems to running and hashing (19DVivDqGCKQ42AqrPBms5QjiGZy4Y5Ktz). There are other small workers using the same BTC address too.
My questions:
1. would this be a good alternative to the previously setup SG remote solo node awhile back?
2. if yes, could you check if my BTC address is sending hash to US node correctly as if the S5 was located in US?
Thanks
I was playing with my lone s5 to be rented out at MRR.
In Antminer pool settings, will be set to MRR servers, one of them was an Asian node which gave me good ping, around 40ms.
During the setup, I could put it to mine to pools when it was not rented.
Currently pool setup at MRR is set to US solo ckpool node with kano US failover, and seems to running and hashing (19DVivDqGCKQ42AqrPBms5QjiGZy4Y5Ktz). There are other small workers using the same BTC address too.
My questions:
1. would this be a good alternative to the previously setup SG remote solo node awhile back?
2. if yes, could you check if my BTC address is sending hash to US node correctly as if the S5 was located in US?
Thanks
February 09, 2016, 05:45:08 PM
How long did you have it running before you hit 44756831208 ?
Off and on almost a year (it was off most of the summer). That 44G share came just over this past weekend, wish it could have happened sooner!
February 09, 2016, 12:45:07 PM
Due to the recent heat wave here in southern California I've shut off my S3+ solo lottery machine. Although looking at the 144G difficulty and seeing that it will probably jump another 20% this adjustment I may end up leaving it off until the halving and see what happens then. I think it will be a long time before we see another solo block, sadly. 
It's a shame, too, because just the other day I got my best share ever (44G, not too shabby for a single S3+) that would have been a block solve like 8 months ago:
It's a shame, too, because just the other day I got my best share ever (44G, not too shabby for a single S3+) that would have been a block solve like 8 months ago:
Code:
{"hashrate1m": "0", "hashrate5m": "0", "hashrate1hr": "10.2M", "hashrate1d": "307G", "hashrate7d": "410G", "lastupdate": 1455041069, "shares": 179923882, "bestshare": 22299525.791939955, "bestever": 44756831208}
February 09, 2016, 11:54:57 AM
That he was... he had a whole thread about solo mining with his S3: https://bitcointalksearch.org/topic/solo-mining-on-an-s3-with-511-difficulty-here-we-go-update-block-found-1132914
I guess I'll keep my fingers crossed and hope for the best then. Although I've never had my miner go over a best share in the billions it's only ever maxed out around 300 million even after being active and no resets for a month. He seemed to have a very lucky miner capable of hashing into the billions range very quickly. It does make me feel better to see someone on an S3 has found a block. Thanks for posting that link!
February 09, 2016, 10:49:36 AM
I think someone also scored a block with ant s1 about a month or so ago..
February 09, 2016, 10:47:25 AM
That he was... he had a whole thread about solo mining with his S3: https://bitcointalksearch.org/topic/solo-mining-on-an-s3-with-511-difficulty-here-we-go-update-block-found-1132914
February 09, 2016, 10:31:49 AM
As far as I remember, it was a guy with an S3.
He must have been quite the happy chap! February 09, 2016, 10:22:54 AM
As far as I remember, it was a guy with an S3.
February 09, 2016, 10:22:06 AM
Seeing as recently there was a block found with just 15TH I wonder what the lowest hash there has been finding a block in recent times.
February 09, 2016, 10:09:25 AM
Hello ck,
Thank you for the pool .. I have approx 900T on port 3334 for a little while - everything look ok?
I am very much hoping to hit - have some minor disasters to avoid/repair.
Thanks again sir.
February 09, 2016, 04:11:50 AM
The Germany Lotto Group start 1 PHs for 4 days
http://solo.ckpool.org/workers/1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_megalotto
http://solo.ckpool.org/workers/1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_megalotto
February 09, 2016, 03:02:30 AM
I was going to wait till the next block was found before restarting the pools since the updates are only very small low level fixes, but there don't seem to be an awful lot of blocks being found so I'll be restarting them shortly. As always downtime should be negligible with most miners not even failing over.
Restarts complete. This should fix the issue where people find their username gets block as unauthorised.
...
Just tested this and can confirm the main server no longer refuses authorization even when its a backup and using DE as main server. First authenticates ok on DE and starts mining and also authenticates fine now with same address.workername on main server which is a backup without any problems..
Seems that bug is crushed, thank you very much -ck.
Jump to: