KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2435 blocks

[lok8nusa]

thanks shazam and lok8nusa

An afterthought: any 4-pin 120mm fan will work, but it NEEDS to put out at least 240cfm to match the original, which will turn 6000 rpm. You may have to swap the tach and pwm pins on your new one.

[1714206416]

1714206416

[1714206416]

1714206416

[gaud]

do we know what exactly is a hw error ? it makes no sence to me since only 1 board seems to get em out of 3

I believe most of my hw errors are from, temperature/fan timing, and network delays. I also see 1 board more than others
sometimes. In cgminer, and awesome miner, it shows independent temps per board , and if 1of them takes longer than
the set time to "warm up" in operating range, it throws an error. Vise, versa, if it takes too long to cool down when it runs
too hot.

These are most of the errors I've dealt with. I expect them to be better, once the miners are in my basement. They are
out in the ole 30°f garage until then.

yea i keep mine in the ausome cooler box idea never goes above 61°C on the hottest board.

[BSGMiner]

So, what was up with the 37 minute shift? Did I miss something?

[BSGMiner]

Welcome AusFreak!

Looks like we may soon have another contender for a 1/2 BTC block reward giveaway!

Come & git it!

[kano]

So, what was up with the 37 minute shift? Did I miss something?

Diff change.
[2018-03-05 14:25:59.664+11] workinfo_add(): DIFF CHANGE: hi=512064 delta=9.42% new=3290605988755.0 prev=3007383866429.7

High yet again coz Bitmain's new miners are coming online in their data centres.

[kano]

do we know what exactly is a hw error ? it makes no sence to me since only 1 board seems to get em out of 3

I believe most of my hw errors are from, temperature/fan timing, and network delays.
...

Network has nothing to do with hardware errors.
A HW error is internal to the miner - somewhere in the process of passing data from the chips back to bmminer, a checksum or counter is wrong.
Note also that Bitmain miners hide a lot of the hardware errors

[gaud]

do we know what exactly is a hw error ? it makes no sence to me since only 1 board seems to get em out of 3

I believe most of my hw errors are from, temperature/fan timing, and network delays.
...

Network has nothing to do with hardware errors.
A HW error is internal to the miner - somewhere in the process of passing data from the chips back to bmminer, a checksum or counter is wrong.
Note also that Bitmain miners hide a lot of the hardware errors

yea seems alot hate bitman was jst curious why always on the first hash board if seen alot of people pics of the same issue alwys on the first hash board

[kano]

do we know what exactly is a hw error ? it makes no sence to me since only 1 board seems to get em out of 3

I believe most of my hw errors are from, temperature/fan timing, and network delays.
...

Network has nothing to do with hardware errors.
A HW error is internal to the miner - somewhere in the process of passing data from the chips back to bmminer, a checksum or counter is wrong.
Note also that Bitmain miners hide a lot of the hardware errors

yea seems alot hate bitman was jst curious why always on the first hash board if seen alot of people pics of the same issue alwys on the first hash board

Um ... that's facts I've stated there

I've posted about the issues with their code and also put in a public git updates to fix their code years ago - S1, S2, S3.
They do seem to have at least finally stopped hiding stale shares with the S9 ... since that also meant throwing away possible blocks

As for which hash board gets the most errors, well you'd need to take a much larger sample to be sure that there's a pattern there.
Remember there's probably at least 10EH of S9s out there ... i.e. probably at least 0.75 million of them

[BSGMiner]

So, what was up with the 37 minute shift? Did I miss something?

Diff change.
[2018-03-05 14:25:59.664+11] workinfo_add(): DIFF CHANGE: hi=512064 delta=9.42% new=3290605988755.0 prev=3007383866429.7

High yet again coz Bitmain's new miners are coming online in their data centres.

Ugh... ~10% increase.

Isn't there a possibility of the difficulty lowering if a lot of these New Year's Resolution miners give up already?

[kano]

So, what was up with the 37 minute shift? Did I miss something?

Diff change.
[2018-03-05 14:25:59.664+11] workinfo_add(): DIFF CHANGE: hi=512064 delta=9.42% new=3290605988755.0 prev=3007383866429.7

High yet again coz Bitmain's new miners are coming online in their data centres.

Ugh... ~10% increase.

Isn't there a possibility of the difficulty lowering if a lot of these New Year's Resolution miners give up already?

Not likely - they'd sell their miners to someone else who'd use them.
... and if they didn't sell them, but just switched them off, there'd have to be more of them switched off, than new miners coming online.

[Shazam!!!]

do we know what exactly is a hw error ? it makes no sence to me since only 1 board seems to get em out of 3

I believe most of my hw errors are from, temperature/fan timing, and network delays.
...

Network has nothing to do with hardware errors.
A HW error is internal to the miner - somewhere in the process of passing data from the chips back to bmminer, a checksum or counter is wrong.
Note also that Bitmain miners hide a lot of the hardware errors

Good info. I mentioned network, in my situation, because when my miners drop signal, they have a tendency to get cold quickly.
When that happens, I can literally watch errors go up with the temp, when the signal reconnects. I chalk it up to 15°f nights, and
a crappy Internet Provider.

[BSGMiner]

So, what was up with the 37 minute shift? Did I miss something?

Diff change.
[2018-03-05 14:25:59.664+11] workinfo_add(): DIFF CHANGE: hi=512064 delta=9.42% new=3290605988755.0 prev=3007383866429.7

High yet again coz Bitmain's new miners are coming online in their data centres.

Ugh... ~10% increase.

Isn't there a possibility of the difficulty lowering if a lot of these New Year's Resolution miners give up already?

Not likely - they'd sell their miners to someone else who'd use them.
... and if they didn't sell them, but just switched them off, there'd have to be more of them switched off, than new miners coming online.

Good point. I guess I'll need to do my part and buy some of the ones they're selling and point them here.

[kano]

do we know what exactly is a hw error ? it makes no sence to me since only 1 board seems to get em out of 3

I believe most of my hw errors are from, temperature/fan timing, and network delays.
...

Network has nothing to do with hardware errors.
A HW error is internal to the miner - somewhere in the process of passing data from the chips back to bmminer, a checksum or counter is wrong.
Note also that Bitmain miners hide a lot of the hardware errors

Good info. I mentioned network, in my situation, because when my miners drop signal, they have a tendency to get cold quickly.
When that happens, I can literally watch errors go up with the temp, when the signal reconnects. I chalk it up to 15°f nights, and
a crappy Internet Provider.

Ah OK - well I guess then network can indirectly relate to HW errors

[clgrissom3]

do we know what exactly is a hw error ? it makes no sence to me since only 1 board seems to get em out of 3

I believe most of my hw errors are from, temperature/fan timing, and network delays.
...

Network has nothing to do with hardware errors.
A HW error is internal to the miner - somewhere in the process of passing data from the chips back to bmminer, a checksum or counter is wrong.
Note also that Bitmain miners hide a lot of the hardware errors

yea seems alot hate bitman was jst curious why always on the first hash board if seen alot of people pics of the same issue alwys on the first hash board

Um ... that's facts I've stated there

I've posted about the issues with their code and also put in a public git updates to fix their code years ago - S1, S2, S3.
They do seem to have at least finally stopped hiding stale shares with the S9 ... since that also meant throwing away possible blocks

As for which hash board gets the most errors, well you'd need to take a much larger sample to be sure that there's a pattern there.
Remember there's probably at least 10EH of S9s out there ... i.e. probably at least 0.75 million of them

I have 2 S9s with the middle board getting the most errors and 3 S9s with the 3rd board getting the most errors.

[padrinogtr]

Welp, my plan took a dive. I'm gonna tweak my rules a bit and give it one last shot before I call it off because it's going to get lost in the pages anyway. I think the changes will open it up to a lot more miners who may have a good answer (including NEW miners).

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
BTC 50 TH/s giveaway !!!! BTC


I want to see how well the small miners understand this and can explain it on a level where YOU(and others, including myself) fully understand it. I want that light bulb to go off and have ZERO doubt about how we are getting paid for our shares and I will donate 50 TH/s for a period of 5 days to a lucky winner.

My rules:

1- You have to have been mining on Kano's Pool with a hash rate between 1 and 20 TH/s
2- The rewarded hash has to be pointed at Kano's pool.  (to be confirmed by Kano)
3- You have to submit your answer in response to this quote and give 2 working examples including the payouts calculated.
4- padrinogtr will have to be able to explain his new understanding with his own example in response to the submitted answer and have the answer's accuracy verified by Kano.
5- New miners to the pool are welcome, though you will have had to have been here for at least the last block (this will help ramp your 5Nd up much sooner!!)

The 5 day 50 TH/s award will start as soon as I am able to see confirmation and have access to my controllers. I will of course need a worker name.
I understand this is dependent on some cooperation from others, but hey it's 50 TH/s on the line and I'm currently only running about 70 TH/s, so it's a big deal to me.

5 days - 50 TH/s .... don't let us down padrinogtr!!!!!! There was talk of others donating some hash too. If their offer is still good, that hash will be separate and in addition to the 50 TH/s I am donating.

*Of course, this is for fun and in the event of a hash rate failure, I will not be obligated to make it up as noted in prior promotions. I hope I'm not leaving out any details. I will stay active with the announcements as well as open to hearing some feedback or details that should be edited.


Thanks everyone and MINE ON!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

You set rules and mentioned an answer but didn't mention a question, so im gonna assume the answer is 42.

Oops! I copied and edited the original which was following a quote. I can't fix it at this point in time, I'll have to come back to that.

The competition is basically to explain the 5Nd in the simplest form. There have been many explanations, but it is still somewhat of a mystery to many. It was in response to a certain member (padrinogtr) not being able to get it no matter what. He has to understand the answer in a way that he can explain it to others. I'm assuming he's a he...

Ok... Last try. Put your thinking cap on Padrinogtr!  

Ground Rules:
For example purposes only, we'll assume that the pool always creates a new block at exactly the 100% expected amount of Network Difficulty in exactly a one (1) week time-period--Yes, I know it's not time-bound.
Also, I will be mixing some of the analogy's terms into the actual explanation just to keep with the flow of thought.

Analogy:
Here's the very best and easiest way I can explain it using something that we should all be familiar with: Employment

*** Does anyone remember when employers used to hold your first week's paycheck?!

Due to this payout method, you were always technically a paycheck behind, but you never lost any money in the deal since they were just delaying it slightly, and even after you left the job, you still could count on having another paycheck that you were owed from when they held your first week's pay.

Now, imagine that they didn't hold your entire first check; just 4/5 of it. Then, each payday that rolls around afterward, they withhold less (3/5) and less (2/5) of each new paycheck until after five (5) paydays, you are now receiving your entire paycheck. In the back of your mind, though, you know that even if you left, you'd still have all that back-pay coming to you.

Explanation:
The PPLNS (5Nd) payout method is very much like this since when the first block that you've helped attempt to solve gets created, the payout process will look back five (5) "weeks" and see that you only worked 1/5 of that time period. Now, when the pool creates the second block that you've contributed to, you've now contributed two (2) out of the past five (5) "weeks", and so on and so forth until you've worked on five (5) consecutive blocks, at which point, you will now be fully ramped up and getting entire "paychecks". On the other hand, if you ever decide to stop mining, the same process would take place in reverse due to the same look-back over the past 5Nd sliding window.

Visual Aide:
Many have attempted to visually represent the ramp-up/ramp-down process, but I'll try to change it up and apply it to the example above since we're all familiar with how weekly paychecks work.

Legend:
O = Times when you weren't mining
M = Times when you were mining
* = When a new block is created (payday)

Calendar:
   SMTWTFS
1  OOOOOOO----|
2  OOOOOOO    |
3  OOOOOOO    |-->1/5
4  OOOOOOO    |
5  MMMMMMM*---|

   SMTWTFS
2  OOOOOOO----|
3  OOOOOOO    |
4  OOOOOOO    |-->2/5
5  MMMMMMM*   |
6  MMMMMMM*---|

   SMTWTFS
3  OOOOOOO----|
4  OOOOOOO    |
5  MMMMMMM*   |-->3/5
6  MMMMMMM*   |
7  MMMMMMM*---|

   SMTWTFS
4  OOOOOOO----|
5  MMMMMMM*   |
6  MMMMMMM*   |-->4/5
7  MMMMMMM*   |
8  MMMMMMM*---|

   SMTWTFS
5  MMMMMMM*---|
6  MMMMMMM*   |
7  MMMMMMM*   |-->5/5
8  MMMMMMM*   |
9  MMMMMMM*---|

   SMTWTFS
6  MMMMMMM*---|
7  MMMMMMM*   |
8  MMMMMMM*   |-->4/5
9  MMMMMMM*   |
10 OOOOOOO*---|

   SMTWTFS
7  MMMMMMM*---|
8  MMMMMMM*   |
9  MMMMMMM*   |-->3/5
10 OOOOOOO*   |
11 OOOOOOO*---|

   SMTWTFS
8  MMMMMMM*---|
9  MMMMMMM*   |
10 OOOOOOO*   |-->2/5
11 OOOOOOO*   |
12 OOOOOOO*---|

   SMTWTFS
9  MMMMMMM*---|
10 OOOOOOO*   |
11 OOOOOOO*   |-->1/5
12 OOOOOOO*   |
13 OOOOOOO*---|


That's it! I don't know how I could do it any better. I'm leaving it all on the [forum] here. It's up to you now Padrinogtr. Good luck!

EDIT: Sorry, I did think to add examples of payout calculations for completeness' sake--Contains super-small rounding errors...

Rewards:
1/5 Payout:
Block: 505456
Block UTC: 22/Jan 03:00
Miner Reward: 15.06656796
N Diff: 11.159T * 1,000,000,000,000 = 11,159,000,000,000
N Range: 407hr 24m 33s
Pool N Avg: 32.68PHs
Your %: 0.00%
Your N Diff: 94.257M * 1,000,000 = 94,257,000
Your N Avg: 276.02GHs
Your BTC: 0.00012725

Equation:
Your N Diff / N Diff = Your % * Miner Reward = Your BTC
94,257,000 / 11,159,000,000,000 = 0.0000084467246169011560175642978761538 * 15.06656796 = 0.00012726315047994623174119544752804

5/5 Payout:
Block: 508425
Block UTC: 9/Feb 20:11
Miner Reward: 12.44363511
N Diff: 14.378T * 1,000,000,000,000 = 14,378,000,000,000
N Range: 366hr 33m 46s
Pool N Avg: 46.80PHs
Your %: 0.01%
Your N Diff: 1.120G * 1,000,000,000 = 1,120,000,000
Your N Avg: 3.64THs
Your BTC: 0.00096921

Equation:
Your N Diff / N Diff = Your % * Miner Reward = Your BTC
1,120,000,000 / 14,378,000,000,000 = 0.00007789678675754625121713729308666 * 12.44363511= 0.00096931919065238558909444985394352

this one is looking really good
ill put my thinking cap on it asap

thanks for the effort

[nazzer]

Definitely maybe before the day is done!

C'mon Monday BTClock!

[clgrissom3]

...clipped...

this one is looking really good
ill put my thinking cap on it asap

thanks for the effort

Could we all start clipping these really long posts?  This one nearly fills the whole page by itself 

[rifleman74]

...clipped...

this one is looking really good
ill put my thinking cap on it asap

thanks for the effort

Could we all start clipping these really long posts?  This one nearly fills the whole page by itself 

ENOUGH WITH THE CLIPPING, MORE WITH THE CRACKING!


MINE ON WITH KANO-SAN!

[BSGMiner]

...clipped...
this one is looking really good
ill put my thinking cap on it asap

thanks for the effort

Could we all start clipping these really long posts?  This one nearly fills the whole page by itself 

Sorry, I had verbose mode on when I wrote that one up.

[BSGMiner]

So, what was up with the 37 minute shift? Did I miss something?

Diff change.
[2018-03-05 14:25:59.664+11] workinfo_add(): DIFF CHANGE: hi=512064 delta=9.42% new=3290605988755.0 prev=3007383866429.7

High yet again coz Bitmain's new miners are coming online in their data centres.

Also, could we add another to-do at the bottom of the backlog to put an indicator on the Shifts page when diff changes and restarts cause a shortened shift (similar to how you indicate blocks)? Thanks