 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
|
These blocks are not paid?
539144 2018-Aug-30 04:39 12.41098323 33.707T 200hr 23m 51s 200.67PHs 0.00% 233.931M 1.39THs 0.00008613
538852 2018-Aug-28 04:50 12.53292048 33.756T 206hr 17m 2s 195.23PHs 0.00% 195.575M 1.13THs 0.00007261
538751 2018-Aug-27 16:57 12.96019670 33.695T 207hr 11m 44s 194.02PHs 0.00% 196.793M 1.13THs 0.00007569
538670 2018-Aug-27 04:17 12.43137567 33.679T 207hr 44m 11s 193.42PHs 0.00% 207.975M 1.19THs 0.00007676
538464 2018-Aug-26 00:54 12.39296456 33.758T 208hr 24m 1s 193.26PHs 0.00% 242.576M 1.39THs 0.00008905
|
|
|
|
the question is closed  patience in explanations is surprising |
|
|
|
Why is the Mem Pool slammed. Is it because only 5% of the BTC Network is signaling for SEGWIT?
The whole network has enabled SegWit. SegWit is a lie. I agree with this, and not only me. |
|
|
|
|
It will not get anywhere? Sorry for my english.
497605 1Gic6xCu8vTMwHYWhFowaztXAfR9fR7ra 0.00009081 *
497299 1Gic6xCu8vTMwHYWhFowaztXAfR9fR7ra 0.00001986 *
little thing, but....
|
|
|
|
|
Has everyone received a payment for the last block?
|
|
|
|
|
Hello, three blocks fell from the statistics, 414909, 414938, 415481, it can be fixed?
|
|
|
|
|
Stopped working? Notification and information from site kano.is all zeros.
|
|
|
|
|
Bad miners have done it on real hardware (ASIC), or through contracts (nicehash)?...
|
|
|
|
|
So what is the actual problem? Irregular payment of these miners? Explain what they did.
|
|
|
|
|
402342 402347 block's not send?
|
|
|
|
Поздравляю Фендер с почином  Congratulations Fender a first block |
|
|
|
|
Site kano.is no working more?
|
|
|
|
I noticed that, constant diff (for S7 set 20k in "Workers\Management"):
397438 8/Feb 22:10 24.96438632 730.646G 39hr 58m 56s 21.80PHs 0.06% 415.474M 12.40THs
397279 7/Feb 20:48 24.94621895 721.188G 40hr 28m 43s 21.26PHs 0.06% 420.763M 12.40THs
397238 7/Feb 15:52 24.80670238 724.086G 41hr 2m 34s 21.05PHs 0.06% 426.759M 12.41THs
and variable (vardiff "0"):
397818 11/Feb 03:05 25.28178578 731.051G 41hr 10m 46s 21.18PHs 0.06% 414.693M 12.01THs
397747 10/Feb 16:59 25.21331413 727.871G 41hr 17m 54s 21.03PHs 0.06% 415.750M 12.01THs
397723 10/Feb 13:25 24.93550825 721.073G 40hr 49m 32s 21.07PHs 0.06% 411.102M 12.01THs
but what better, fixed diff or vardiff?
Neither of those are related directly to hash rate. They are related directly, only, to how much of the elapsed time of the 5Nd you mined, which may not have been the full time depending upon various circumstances with your miner and the pool. Edit: or you could just look at the pool graph and see a spike down that is part of the 2nd 3 and not part of the first 3 See here: https://bitcointalk.org/index.php?topic=789369.msg13831674#msg13831674Lastly you will also note that your % is the same for each of the 6 - try checking that to a few extra places. That would give the same explanation also. It blocks a row, not selectively, I do not think that a row spike down 3-5 bloks...  Left select - fixed diff, right select - 0(vardiff) Actually, since this is a 5Nd pool, any large spike up or down will have an effect on the next 3-5 blocks...that's how 5Nd works. Bottom line is over the long haul it will not matter which way you set it so pick vardiff or fixed diff and have at it. The default is vardiff and it has worked well for me over time. I personally trust kano and ck to know how to run the best pool environment possible...bar none! I am trust too, in case of replace the pool...See: 397818 11/Feb 03:05 25.28178578 731.051G 41hr 10m 46s 21.18PHs 0.06% 414.693M 12.01THs 397747 10/Feb 16:59 25.21331413 727.871G 41hr 17m 54s 21.03PHs 0.06% 415.750M 12.01THs 397723 10/Feb 13:25 24.93550825 721.073G 40hr 49m 32s 21.07PHs 0.06% 411.102M 12.01THs 397649 10/Feb 02:39 25.02525347 724.414G 40hr 45m 48s 21.20PHs 0.06% 414.845M 12.14THs 397628 10/Feb 00:22 25.10738938 726.052G 40hr 50m 25s 21.21PHs 0.06% 417.485M 12.20THs 397511 9/Feb 08:26 25.10888855 726.812G 39hr 47m 13s 21.79PHs 0.06% 412.734M 12.38THs 397486 9/Feb 04:55 24.94781485 734.550G 40hr 13m 30s 21.79PHs 0.06% 418.219M 12.40THs 397438 8/Feb 22:10 24.96438632 730.646G 39hr 58m 56s 21.80PHs 0.06% 415.474M 12.40THs 397279 7/Feb 20:48 24.94621895 721.188G 40hr 28m 43s 21.26PHs 0.06% 420.763M 12.40THs 397238 7/Feb 15:52 24.80670238 724.086G 41hr 2m 34s 21.05PHs 0.06% 426.759M 12.41THs Blocks 397238-397486 fixed diff, rest changed when to vardiff...less and less...why have a question that is best...And other, when put into difficulty 0, in the asic diff is not changed, but 02.10.2016 when the pool is not working some time asic's changed diff, vardiff turn on...This put on one's guard what is a better. |
|
|
|
I noticed that, constant diff (for S7 set 20k in "Workers\Management"):
397438 8/Feb 22:10 24.96438632 730.646G 39hr 58m 56s 21.80PHs 0.06% 415.474M 12.40THs
397279 7/Feb 20:48 24.94621895 721.188G 40hr 28m 43s 21.26PHs 0.06% 420.763M 12.40THs
397238 7/Feb 15:52 24.80670238 724.086G 41hr 2m 34s 21.05PHs 0.06% 426.759M 12.41THs
and variable (vardiff "0"):
397818 11/Feb 03:05 25.28178578 731.051G 41hr 10m 46s 21.18PHs 0.06% 414.693M 12.01THs
397747 10/Feb 16:59 25.21331413 727.871G 41hr 17m 54s 21.03PHs 0.06% 415.750M 12.01THs
397723 10/Feb 13:25 24.93550825 721.073G 40hr 49m 32s 21.07PHs 0.06% 411.102M 12.01THs
but what better, fixed diff or vardiff?
Neither of those are related directly to hash rate. They are related directly, only, to how much of the elapsed time of the 5Nd you mined, which may not have been the full time depending upon various circumstances with your miner and the pool. Edit: or you could just look at the pool graph and see a spike down that is part of the 2nd 3 and not part of the first 3 See here: https://bitcointalk.org/index.php?topic=789369.msg13831674#msg13831674Lastly you will also note that your % is the same for each of the 6 - try checking that to a few extra places. That would give the same explanation also. It blocks a row, not selectively, I do not think that a row spike down 3-5 bloks... Left select - fixed diff, right select - 0(vardiff) |
|
|
|
|
I noticed that, constant diff (for S7 set 20k in "Workers\Management"):
397438 8/Feb 22:10 24.96438632 730.646G 39hr 58m 56s 21.80PHs 0.06% 415.474M 12.40THs
397279 7/Feb 20:48 24.94621895 721.188G 40hr 28m 43s 21.26PHs 0.06% 420.763M 12.40THs
397238 7/Feb 15:52 24.80670238 724.086G 41hr 2m 34s 21.05PHs 0.06% 426.759M 12.41THs
and variable (vardiff "0"):
397818 11/Feb 03:05 25.28178578 731.051G 41hr 10m 46s 21.18PHs 0.06% 414.693M 12.01THs
397747 10/Feb 16:59 25.21331413 727.871G 41hr 17m 54s 21.03PHs 0.06% 415.750M 12.01THs
397723 10/Feb 13:25 24.93550825 721.073G 40hr 49m 32s 21.07PHs 0.06% 411.102M 12.01THs
but what better, fixed diff or vardiff?
|
|
|
|
|
Question, I wrote 20000 diff in "Workers\Management"? Then changed to 0, but asic reports that diff 20000, vardiff does not work? Rebooted, "off" then "on", same 20000.
|
|
|
|
|
Now just an orphan
397182 Dsman_S7_3 25.23924789 2016-02-07 09:01:52+00 Orphan *~0 ? ? 0
|
|
|
|
|
