Author

Topic: [∞ YH] solo.ckpool.org 2% fee solo mining USA/DE 255 blocks solved! - page 224. (Read 1514767 times)

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Code:
[2016-02-06 02:35:15.481] Possible block solve diff 408910813208.166382 !
[2016-02-06 02:35:15.589] BLOCK ACCEPTED!
[2016-02-06 02:35:15.590] Solved and confirmed block 396990 by 1BY56HUVrmr5k6GLeuDYo98NdvgxjxxZcc.AntMiner5
[2016-02-06 02:35:15.590] User 1BY56HUVrmr5k6GLeuDYo98NdvgxjxxZcc:{"hashrate1m": "15.8T", "hashrate5m": "14.7T", "hashrate1hr": "14.4T", "hashrate1d": "5.27T", "hashrate7d": "907G"}
[2016-02-06 02:35:15.590] Worker 1BY56HUVrmr5k6GLeuDYo98NdvgxjxxZcc.AntMiner5:{"hashrate1m": "5T", "hashrate5m": "4.89T", "hashrate1hr": "4.74T", "hashrate1d": "4.71T", "hashrate7d": "3.8T"}
[2016-02-06 02:35:15.590] Block solved after 15376037314 shares at 12.8% diff

https://www.blocktrail.com/BTC/block/000000000000000002b057ac869b136e48f0c93e37ab2c1578a20cecc20f0b5f

15TH miner!
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/

Code:
[2016-02-06 02:30:34.631] Possible block solve diff 655117758757.222900 !
[2016-02-06 02:30:34.894] BLOCK ACCEPTED!
[2016-02-06 02:30:34.896] Solved and confirmed block 396941 by 1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_megalotto
[2016-02-06 02:30:34.896] User 1Q8VghUJkNeFnaKy553b9buUWKxFYL579G:{"hashrate1m": "923T", "hashrate5m": "905T", "hashrate1hr": "959T", "hashrate1d": "185T", "hashrate7d": "28.9T"}
[2016-02-06 02:30:34.896] Worker 1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_megalotto:{"hashrate1m": "923T", "hashrate5m": "905T", "hashrate1hr": "967T", "hashrate1d": "1.06P", "hashrate7d": "478T"}
[2016-02-05 20:30:36.818] Block solved after 323903866863 shares at 269.8% diff

member
Activity: 110
Merit: 10
newbie
Activity: 48
Merit: 0
Those damn Germans lol guess they finally found one.

{"hashrate1m": "935T", "hashrate5m": "915T", "hashrate1hr": "958T", "hashrate1d": "182T", "hashrate7d": "28.4T", "lastupdate": 1454725934, "workers": 7, "shares": 4052487343, "bestshare": 43597868.270617001, "bestever": 655117758757, "worker": [{"hashrate1m": "935T", "hashrate5m": "915T", "hashrate1hr": "965T", "hashrate1d": "1.06P", "hashrate7d": "477T", "lastupdate": 1454725934, "shares": 87480025878, "bestshare": 43597868.270617001, "bestever": 655117758757, "workername": "1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_megalotto"}]}

wonder if they will break even? and donate to -ck this time.. lol

gotta spend some to make some...ugh! I hope lady luck pays me a visit some day Smiley
member
Activity: 66
Merit: 10
Those damn Germans lol guess they finally found one.

{"hashrate1m": "935T", "hashrate5m": "915T", "hashrate1hr": "958T", "hashrate1d": "182T", "hashrate7d": "28.4T", "lastupdate": 1454725934, "workers": 7, "shares": 4052487343, "bestshare": 43597868.270617001, "bestever": 655117758757, "worker": [{"hashrate1m": "935T", "hashrate5m": "915T", "hashrate1hr": "965T", "hashrate1d": "1.06P", "hashrate7d": "477T", "lastupdate": 1454725934, "shares": 87480025878, "bestshare": 43597868.270617001, "bestever": 655117758757, "workername": "1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_megalotto"}]}

wonder if they will break even? and donate to -ck this time.. lol
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
legendary
Activity: 872
Merit: 1010
Coins, Games & Miners
...

That's odd, you shouldn't be getting that with this pool. Which server/port are you pointing them to and what version of ckproxy? You should be using the latest git master.

EDIT: I'm guessing you have other pools in your configuration and they're the ones it's complaining about.

No, there's no warning right now, just the warnings i read on the README and such that piqued my curiosity.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
...

Restarts complete. This should fix the issue where people find their username gets block as unauthorised.


By the way, just deployed two instances of ckproxy to interface to ckpool, and found a lot of warnings about "high" hashrate of the proxy not working with standard pools, how high is "high" and should i worry with 26 THs?
That's odd, you shouldn't be getting that with this pool. Which server/port are you pointing them to and what version of ckproxy? You should be using the latest git master.

EDIT: I'm guessing you have other pools in your configuration and they're the ones it's complaining about.
legendary
Activity: 872
Merit: 1010
Coins, Games & Miners
...

Restarts complete. This should fix the issue where people find their username gets block as unauthorised.


By the way, just deployed two instances of ckproxy to interface to ckpool, and found a lot of warnings about "high" hashrate of the proxy not working with standard pools, how high is "high" and should i worry with 26 THs?
newbie
Activity: 48
Merit: 0
Yes, if you have a bunch of miners at home, you would solo mine to the BTC wallet if you wanted.

Yes that's correct. The pool's total hashrate is only useful to me. Your chance of finding a block is completely independent of the pool's hashrate, time since last block found, etc.

Much appreciated!
legendary
Activity: 2702
Merit: 1030
Yes I am a pirate, 300 years too late!
Your last sentence is correct.  It was a lucky gamble.  800TH/s expects to take about 7.5 days to find a block at current difficulty.  Congrats on the hit, though!

 Grin thanks, that being said though i was ~1/3 the pools power so combing pool hash power plus the time since the last block solved by the pool, the odds were a little more to my favor. but still lucky as hell..
No, sorry that's wrong. The total pool's hashrate and the duration since the last block have precisely zero effect on your chance of finding a block. Only your hashrate matters. I will keep saying this over and over. If you have a "system" in your head for how to gamble based on current pool hashrate, time since last block, predicting when and where the next block will be etc., that's your business, but please don't try to tell people that it's fact or scientific.

Thanks for clarifying that! Being new to the whole experience I would have thought total pool hash rate would have influenced speed in finding the next block. So, basically the total pool hash rate just shows the amount that's being produced as a whole, but it's the individual's hashing power that matters in their luck in finding a block?

Yes, if you have a bunch of miners at home, you would solo mine to the BTC wallet if you wanted.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
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.

Thanks for clarifying that! Being new to the whole experience I would have thought total pool hash rate would have influenced speed in finding the next block. So, basically the total pool hash rate just shows the amount that's being produced as a whole, but it's the individual's hashing power that matters in their luck in finding a block?

Yes that's correct. The pool's total hashrate is only useful to me. Your chance of finding a block is completely independent of the pool's hashrate, time since last block found, etc.
newbie
Activity: 48
Merit: 0
Your last sentence is correct.  It was a lucky gamble.  800TH/s expects to take about 7.5 days to find a block at current difficulty.  Congrats on the hit, though!

 Grin thanks, that being said though i was ~1/3 the pools power so combing pool hash power plus the time since the last block solved by the pool, the odds were a little more to my favor. but still lucky as hell..
No, sorry that's wrong. The total pool's hashrate and the duration since the last block have precisely zero effect on your chance of finding a block. Only your hashrate matters. I will keep saying this over and over. If you have a "system" in your head for how to gamble based on current pool hashrate, time since last block, predicting when and where the next block will be etc., that's your business, but please don't try to tell people that it's fact or scientific.

Thanks for clarifying that! Being new to the whole experience I would have thought total pool hash rate would have influenced speed in finding the next block. So, basically the total pool hash rate just shows the amount that's being produced as a whole, but it's the individual's hashing power that matters in their luck in finding a block?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
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.
sr. member
Activity: 419
Merit: 250
Hmm that reminds me I've had this problem before. If you authed first on the DE pool you cannot auth on the main pool later on. I thought I'd fixed this bug but it seems to have returned. That would explain it. I'll look into it.
Is this related to a bug I posted about a couple weeks ago?  Well, I guess I don't know if it's a bug or a flaw in the way the miner operates, but just wondering.

The IP address of solo.ckpool.org changes after a DDoS and perhaps these devices almost never look up the IP address using a cached result for ages. In which case a restart might be required, either of cgminer or the whole device.
I have restarted the whole device 3 times (one of those was power off for 20+ minutes) and it still is in failover, I'll see if I can't flush its dns cache or something, thanks.
I had the same bug a couple of weeks back, all I had to do was change the address I was mining to.
I could not locate any sort of dns reset in the S3 interface so I tried changing addresses and the pool was ALIVE again.  I changed back to the old address thinking maybe I had cleared up the issue, but the old address reports the pool as DEAD.  A new solo address for the US node it is then!  Problem solved, thanks.

Changed mining to a new address and all seems to be well. Note that it had to be an entire new address, not just worker name. (so now I have different addresses for DE and main, but I suppose that's OK)
legendary
Activity: 3583
Merit: 1094
Think for yourself
Update:
We are still hashing with 1PH yesteday we tryed 5PH for 4Hours but the Bestshare dont change.
http://solo.ckpool.org/workers/1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_megalotto

"bestshare": 99850230440.55542

Wish us Luck for today guys Smiley

Bestshare will change only when is a new block found

Best share will change when a higher diff share is found.  It is reset on block find.  Best ever is sticky through blocks.
legendary
Activity: 1161
Merit: 1001
Don`t invest more than you can afford to lose
Update:
We are still hashing with 1PH yesteday we tryed 5PH for 4Hours but the Bestshare dont change.
http://solo.ckpool.org/workers/1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_megalotto

"bestshare": 99850230440.55542

Wish us Luck for today guys Smiley

Bestshare will change only when is a new block found
sr. member
Activity: 283
Merit: 250
Update:
We are still hashing with 1PH yesteday we tryed 5PH for 4Hours but the Bestshare dont change.
http://solo.ckpool.org/workers/1Q8VghUJkNeFnaKy553b9buUWKxFYL579G_megalotto

"bestshare": 99850230440.55542

Wish us Luck for today guys Smiley
member
Activity: 66
Merit: 10
gonna try my luck with 3 antminer s1 mayaswell have a bash for a while Smiley

good luck
member
Activity: 112
Merit: 10
gonna try my luck with 3 antminer s1 mayaswell have a bash for a while Smiley
Jump to: