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

[wmabern]

Put my four S9's back on the pool for the foreseeable future. 
I know it's nothing massive, but every little 50TH helps! Wish I had double that hash.

(I was only running the three S7's on the pool, partly as space heaters for the far-reaches of the house and to help out a little bit with hash for the pool. However it's gotten too warm around here to run them. The heat in the house even with the windows open is unbearable! )

So, I've put the four S9's from the "coin room" back on Kano. They have good air flow in and out, so the temps are all good. I love the pool luck for the month so far. It's a far cry from December! 

Spot coin price made me take a double take when I looked at it today at work. I hope it hold these gains (or increase!) at least till the end of the month. 

Let's get down to some block-cracking!! 
BLOCKSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!!!!!!!

CHEERS ALL!! 

[1715115401]

1715115401

[Sr.Urbanist]

On the SG node, there was one of those node glitches at 10:07 UTC
Everyone (of the 9 users on the SG node) reconnected immediately, but it was a failover and fail back which takes 5 minutes in cgminer.

I wish there was an emoji for something flying over my head.  I guess this will do:  
I'm glad you know, monitor and share this stuff.  Gracias.

Any idea where geographically?

[Biodom]

On the SG node, there was one of those node glitches at 10:07 UTC
Everyone (of the 9 users on the SG node) reconnected immediately, but it was a failover and fail back which takes 5 minutes in cgminer.

I wish there was an emoji for something flying over my head.  I guess this will do:  
I'm glad you know, monitor and share this stuff.  Gracias.

Any idea where geographically?

sg is singapore, and main server is in Las Vegas, I believe.

[Sr.Urbanist]

sg is singapore, and main server is in Las Vegas, I believe.

Cool.  Gotcha. Thanks. SG. Who can forget them?  It's like the Netherlands, but with fewer bikes (?) ...

[pokapeski]

stuff

A couple of mistakes in there

Time isn't (usually) a factor in rewards.
If the pool hash rate halves, then the pool will find half as many blocks, but your reward per block will double.

The factor that is relevant is difficulty.
As difficulty increases, your expected reward decreases in proportion with the difficulty increase.

Also as Phil has said, electricity cost is one of the main big factors in determining your return.
The other main ones are cost of hardware and reliability of hardware.

Aside: Time becomes a factor if we don't find enough blocks per difficulty change, since then more of your rewards are affected by later difficulty changes.

Thanks kano, and phillip. You are right that the given information is not complete. It was quite late yesterday as I wrote that.
I do understand the energy cost is the main factor here together with the infra cost to hit ROI asap so that's why these 2 variables are important in my opinion.
1/ The first column is average number of hours to find a block by the pool (and get paid). Energy price is a given data. it's a constant practically. there is not much i can do about it at this point so the variable that makes me make profit or not is actually the number of hours that the equipment takes to make coins. (the point of ignorance on my side is if the number of hours you are mining affects the amount of money you make. My understanding is that only the relative hash power to the pool (column2) and the speed in which blocks are found are the 2 main variables that determine how much I make per day in average.
Why am I considering mining not a long run thing with this data? because the curve shows increasing times in the pool. (I know luck is a variable but as you cannot affect it it's wise not to think much of it)

2/ The second column is average number of hashes to find a block, as I know how many hashes/s I have this tries to measure how un/important is my share of work and how it's evolving given the difficulty. That is, how many calculations are actually made for one reason or another in every block as average. This column is not nice in my opinion and affects you infra investment as in a very short period it's in its way to double the numbers from the summer and, as mentioned in my previous post, there are quite a few more s9 comming in shortly.
Why am I considering mining not a long run thing with this data? because you want to keep up with lineal slope of this trend to make the money you were making yesterday.

seeing this in the table is quite arid, I know, unfortunately I cannot upload a pic of the graph to illustrate the points at this moment.

So that's my thinking. I understand they are not the traditional mining ratios but I dont think that it means necessarily that they are not representing a reality. But again, i might be wrong.

[kano]

You missed my first point.
The time the pool takes to find a block is dependent upon the hash rate.

It doesn't matter if the average time doubles when the hash rate halves.
Time isn't the number used anywhere in the calculation of rewards or luck.
The total diff of the total shares is what matters.

If tomorrow the pool hash rate doubled then we'd expect to find twice as many blocks.
But your reward would not increase.
Each block you'd be paid half what you would be getting, vs if the pool hash rate didn't double.

Your hash rate determines your expected reward, not the pool hash rate and not the average time finding blocks.

You can see the pool hash rate history for when you were mining - it shows the hash rate for the 5Nd for each block you get a reward.

... after all that, you then apply diff changes ...

[pokapeski]

You missed my first point.
The time the pool takes to find a block is dependent upon the hash rate.

It doesn't matter if the average time doubles when the hash rate halves.
Time isn't the number used anywhere in the calculation of rewards or luck.
The total diff of the total shares is what matters.

If tomorrow the pool hash rate doubled then we'd expect to find twice as many blocks.
But your reward would not increase.
Each block you'd be paid half what you would be getting, vs if the pool hash rate didn't double.

yup, I failed to mention that the reason for this is calculating to study if investing in more equipment is actually a good thing or I would be better off by just buying bitcoins and letting my money grow with the exchange rate.
That's why in my first post I made reference to hitting the 1 EUR/day*THs of equipment I have.
So that vble. matters to me to make the decission to increase my hash rate as in the big numbers i will hardly be affecting the time but my reward would growing proportionally to the increase i make to my own "production" of hashes.

Your hash rate determines your expected reward, not the pool hash rate and not the average time finding blocks.

You can see the pool hash rate history for when you were mining - it shows the hash rate for the 5Nd for each block you get a reward.

... after all that, you then apply diff changes ...

That's actually I do not quite grasp. What is a "diff"? I failed to find info about it.
Thanks for your answers btw.

[Vegasdude]

Just joined the pool hope all is up and hashing for the pool.... Worker name is LVMining....... Ordered 2 s9's only 1 received so far 13.8 TH/s...so will be doubling in a couple weeks....Thanks for the help earlier....

[kano]

...
So that vble. matters to me to make the decission to increase my hash rate as in the big numbers i will hardly be affecting the time but my reward would growing proportionally to the increase i make to my own "production" of hashes.

Yep, your hash rate is what decides, not the pool's average time to find a block.

Your hash rate determines your expected reward, not the pool hash rate and not the average time finding blocks.

You can see the pool hash rate history for when you were mining - it shows the hash rate for the 5Nd for each block you get a reward.

... after all that, you then apply diff changes ...

That's actually I do not quite grasp. What is a "diff"? I failed to find info about it.
Thanks for your answers btw.

Every 2016 blocks, it (usually) gets harder to find a block.

To find a block, you must find a hash value that is lower than the bitcoin difficulty (on all pools and all miners)
That difficulty is currently 440,779,902,286.5892
So you must find a share with it's "difficulty value" above that number, to find a block.

That number represents a difficulty that means: the average expected time for the power of all miners on the planet, to find a block, is 10 minutes.

Every 2016 blocks (about 2 weeks) bitcoin readjusts the difficulty, based on 2015 of those 2016 past blocks, so that the 10 minute average is expected.

If more miners are added over those 2 weeks then the difficulty gets harder.
If people turn off more miners than are added, then the difficulty may get easier.
Of course, it almost always gets harder.

[flminer]

just a quick curiosity question. how long does it take for payments to be processed after a block is found? 

[kano]

just a quick curiosity question. how long does it take for payments to be processed after a block is found? 

As the payouts page implies, less than 100 blocks.

The coinbase reward in a bitcoin block cannot be spent until 101 confirms i.e. I can't send it until 100 blocks after the block
(which of course I've already done for 454315, it's txnid is 71d174643fef28f78fcdae7ca93a0320cf6249e023dfda498cc133ad01963003)

Thus as it says on the bottom of Help->Payouts on the web site https://kano.is/index.php?k=payout

When are payments sent out?

The block 'Status' must first reach '+101 Confirms' on the Blocks page, and then is flagged as 'Matured', before the reward is distributed.
The block reward transaction is created manually before the block matures, and sent out automatically a minute after the block matures.

The payout uses a zero fee transaction, so we will confirm it with the next block we find after the transaction is sent out.

[kano]

NL just did a failover 09:26 UTC - seems that most of the miners on NL have DE as the backup, which is a good choice, so they failed over to DE, then back again to NL a few minutes later.
All OK again.

Just a point to note for anyone who may be unsure about these events that I've been reporting (for years) and what they mean:
Basically a failover means that a group of miners switched to their backup pool, then switched back again to their first choice pool.
Usually it's immediate, but sometimes can take up to 5 minutes of mining on the backup pool, your 2nd pool configured in the web miner web interface, before switching back to your first choice pool in your miner.
It's a very minor inconvenience, but if your miner is setup properly with backups, it should be no real down time for the miner.

[kano]

Block! by 1JQN...
Probably an S7

Edit: and 454315's payout of course.

[wmabern]

Hi Kano,
Would my IP have gotten blocked sometime overnight? All of my miners were hashing away when I went to bed and this morning all are showing 0 hash. I have rebooted them all and I get the message "Socket connect failed: Connection refused".

I'll PM you my IP if that might be the case. Also, why would they be blocked? Thanks for a quick response so I can make pool changes if need be before I go to work.
Thank you.

Edit: Username: whirledps

[kano]

Hi Kano,
Would my IP have gotten blocked sometime overnight? All of my miners were hashing away when I went to bed and this morning all are showing 0 hash. I have rebooted them all and I get the message "Socket connect failed: Connection refused".

I'll PM you my IP if that might be the case. Also, why would they be blocked? Thanks for a quick response so I can make pool changes if need be before I go to work.
Thank you.

Edit: Username: whirledps

There's no bans or blocks on your IP
Must be a routing problem local to you I guess.

Edit: if you look at your workers page you'll see it happened about 5 hours ago.

[wmabern]

Hi Kano,
Would my IP have gotten blocked sometime overnight? All of my miners were hashing away when I went to bed and this morning all are showing 0 hash. I have rebooted them all and I get the message "Socket connect failed: Connection refused".

I'll PM you my IP if that might be the case. Also, why would they be blocked? Thanks for a quick response so I can make pool changes if need be before I go to work.
Thank you.

Edit: Username: whirledps

There's no bans or blocks on your IP
Must be a routing problem local to you I guess.

Edit: if you look at your workers page you'll see it happened about 5 hours ago.

Thank you. Working on the problem. All of the miners seem like they just stopped 5+ hours a go. I was asleep, so couldn't have done anything to screw them up then. LOL

[kano]

Hi Kano,
Would my IP have gotten blocked sometime overnight? All of my miners were hashing away when I went to bed and this morning all are showing 0 hash. I have rebooted them all and I get the message "Socket connect failed: Connection refused".

I'll PM you my IP if that might be the case. Also, why would they be blocked? Thanks for a quick response so I can make pool changes if need be before I go to work.
Thank you.

Edit: Username: whirledps

There's no bans or blocks on your IP
Must be a routing problem local to you I guess.

Edit: if you look at your workers page you'll see it happened about 5 hours ago.

Thank you. Working on the problem. All of the miners seem like they just stopped 5+ hours a go. I was asleep, so couldn't have done anything to screw them up then. LOL

The traceroute from the passthru to you shows it working to your network provider, but nothing gets past them to you.
Thus it's some problem where your miners are.

[d57heinz]

FYI. For those that may have missed it. Cloud fare has been hacked. All sites using this need to reset their passwords.

BR
d57heinz

From kraken exchange

A bug was recently discovered with Cloudflare, which Kraken and many other websites use for DoS protection and other services. Due to the nature of the bug, we recommend as a precaution that you change your Kraken security credentials:
Change your password
Change your two-factor authentication (remove and re-enable it)
Clients who use API keys should generate a new set of keys

[kano]

... and related to the above, I don't use cloud flare (or any other service) for the web site or anything else on kano.is
I run everything
(so problems only exist if are were issues with the companies I use to provide servers)

[d57heinz]

Here is a growing list of sites affected

https://github.com/pirate/sites-using-cloudflare/blob/master/README.md

BR