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

[kano]

it's getting better now! Thanks for the block, thinking about to add another 200 th/s to kano.

A (noob)-Question:

At my workers, what is:

- Work Diff
- Shares
- «Elapsed after Share Rate

"Work Diff" is the difficulty shares you send to the pool if you want to get a reward, your miner usually gets it right
"Shares" is how many you've sent - it resets each time we find a block.
"«Elapsed" is the amount of time used to calculate the "Share Rate" - it, and share rate, resets every network block - a short time means high variance.
"Share Rate" is simply 2^32 * "DiffE" / "«Elapsed" - where "DiffE" is the Diff submitted during "«Elapsed" - but not shown there.

Everything on that page but "Hash Rate" is accurate to a fraction of a second - as soon as KDB knows about a share, which usually takes microseconds after it arrives at the main pool node, it's there on the page.

[1714079161]

1714079161

[1714079161]

1714079161

[1714079161]

1714079161

[comby]

it's getting better now! Thanks for the block, thinking about to add another 200 th/s to kano.

A (noob)-Question:

At my workers, what is:

- Work Diff
- Shares
- «Elapsed after Share Rate

"Work Diff" is the difficulty shares you send to the pool if you want to get a reward, your miner usually gets it right
"Shares" is how many you've sent - it resets each time we find a block.
"«Elapsed" is the amount of time used to calculate the "Share Rate" - it, and share rate, resets every network block - a short time means high variance.
"Share Rate" is simply 2^32 * "DiffE" / "«Elapsed" - where "DiffE" is the Diff submitted during "«Elapsed" - but not shown there.

Everything on that page but "Hash Rate" is accurate to a fraction of a second - as soon as KDB knows about a share, which usually takes microseconds after it arrives at the main pool node, it's there on the page.

Thank you kano.

So "Work Diff" is actually based on the hashrate/power of a miner?

So the more hashpower, the quicker "Shares" gets up? So if I have a list of 20 miners, the one with the best "Shares Rate" is actually the best miner?

In your API, i actually get "w_hashrate1hr" a value of something like "14146730897086.150391", what is that number? Cannot find any API Doc :/

I read that it's important that miners have a good connection to the pool, how do i idenfity that? Is that "w_active_start" on your API or "Last Share Time" on bmminer ?

thank you!

[kano]

...
Thank you kano.

So "Work Diff" is actually based on the hashrate/power of a miner?

So the more hashpower, the quicker "Shares" gets up? So if I have a list of 20 miners, the one with the best "Shares Rate" is actually the best miner?

In your API, i actually get "w_hashrate1hr" a value of something like "14146730897086.150391", what is that number? Cannot find any API Doc :/

I read that it's important that miners have a good connection to the pool, how do i idenfity that? Is that "w_active_start" on your API or "Last Share Time" on bmminer ?

thank you!

The miner hash rate is used to set the Work Diff - it's not exact, since shares are random like blocks, but there's just a lot more of them.

The best "Share Rate" is just the luck of the miner over the last "«Elapsed", when comparing a bunch of similar miners.
If all miners have very similar hash rates, then it will vary regularly which one has the best "Share Rate"

The point of "Share Rate" is to see how your miner goes when it first connects to the pool, "Hash Rate" can take 15 minutes of more to show something resembling the hash rate, but "Share Rate" gets up near the miner hash rate pretty quickly, but has high variance.

The API hashrate values are hashes per second. So 1TH/s you'd have to divide by 10^12

Good 'connection' means that the ping to the pool is low.
But many pools have no idea of the relevance of that number coz their block change times are high and make the ping time irrelevant.
A ping time under 100ms is good, but even up to 200ms is bearable here.
There's a number of nodes listed in the first post and the thread topic - NL, JP, NYA, DE, SG - pick the one closest to you if you aren't close to West Coast USA.

[comby]

...
Thank you kano.

So "Work Diff" is actually based on the hashrate/power of a miner?

So the more hashpower, the quicker "Shares" gets up? So if I have a list of 20 miners, the one with the best "Shares Rate" is actually the best miner?

In your API, i actually get "w_hashrate1hr" a value of something like "14146730897086.150391", what is that number? Cannot find any API Doc :/

I read that it's important that miners have a good connection to the pool, how do i idenfity that? Is that "w_active_start" on your API or "Last Share Time" on bmminer ?

thank you!

The miner hash rate is used to set the Work Diff - it's not exact, since shares are random like blocks, but there's just a lot more of them.

The best "Share Rate" is just the luck of the miner over the last "«Elapsed", when comparing a bunch of similar miners.
If all miners have very similar hash rates, then it will vary regularly which one has the best "Share Rate"

The point of "Share Rate" is to see how your miner goes when it first connects to the pool, "Hash Rate" can take 15 minutes of more to show something resembling the hash rate, but "Share Rate" gets up near the miner hash rate pretty quickly, but has high variance.

The API hashrate values are hashes per second. So 1TH/s you'd have to divide by 10^12

Good 'connection' means that the ping to the pool is low.
But many pools have no idea of the relevance of that number coz their block change times are high and make the ping time irrelevant.
A ping time under 100ms is good, but even up to 200ms is bearable here.
There's a number of nodes listed in the first post and the thread topic - NL, JP, NYA, DE, SG - pick the one closest to you if you aren't close to West Coast USA.

thank you, i just have seen that a ping to the US server (which is the default) is:

round-trip min/avg/max = 191.508/191.962/200.263 ms

while to an european one:

round-trip min/avg/max = 33.779/33.991/34.206 ms

so i will move!

[jhoren]

So my ping to west coast is 56.* and my ping to east coast is 57.*

[minergain.com]

My biggest fear is somehow losing my coin through the process somehow... That would be devastating.

So you already have a payment address from some wallet on the kano pool?  If you do not have a payment address yet, then Kano will not be paying you until he gets some new "dust" coding complete (hopefully this year).  Your payments will continue to go to the previous wallet so you should not lose your BTC.  Once you get Core running, create a new receive address and change your account to use the new address.  You can also create a new receive address and transfer from your old wallet to the new one.  There are also ways to import private addresses (use your old address) into Bitcoin Core if you want to, but it is confusing plus it takes a couple more hours to scan the blockchain when you do it.

[NotFuzzyWarm]

Ok so I deposited some money on NH I was going to send some extra power to this pool, I can't get it to work though, NH can't seem to connect to this pool on any port. Is there a reason for this?

Several months ago (last year?) when the pool was last this size a lot of it was rental and it turned out a large percentage of that rental hash was either maliciously or unintentionally returning very low quality hash results. Ergo all rental has since been banned from here.

[BSGMiner]

So my ping to west coast is 56.* and my ping to east coast is 57.*

Sounds like you should set one of them as pool 1 and the other as pool 2.

[maddadata]

So my ping to west coast is 56.* and my ping to east coast is 57.*

Sounds like you should set one of them as pool 1 and the other as pool 2.

Also sounds like U r in St. Louis  

[Vlada69]

So my ping to west coast is 56.* and my ping to east coast is 57.*

Sounds like you should set one of them as pool 1 and the other as pool 2.

Also sound like U r in St. Louis 

Just tiny bit to the west

[BSGMiner]

My biggest fear is somehow losing my coin through the process somehow... That would be devastating.

So you already have a payment address from some wallet on the kano pool?  If you do not have a payment address yet, then Kano will not be paying you until he gets some new "dust" coding complete (hopefully this year).  Your payments will continue to go to the previous wallet so you should not lose your BTC.  Once you get Core running, create a new receive address and change your account to use the new address.  You can also create a new receive address and transfer from your old wallet to the new one.  There are also ways to import private addresses (use your old address) into Bitcoin Core if you want to, but it is confusing plus it takes a couple more hours to scan the blockchain when you do it.

Yep. Created handful of offline addresses before I started mining and set one as my dedicated mining address on kano.is. I'm not that noob. Thanks for the extra Core info, though.

[BSGMiner]

"Work Diff" is the difficulty shares you send to the pool if you want to get a reward, your miner usually gets it right
"Shares" is how many you've sent - it resets each time we find a block.
"«Elapsed" is the amount of time used to calculate the "Share Rate" - it, and share rate, resets every network block - a short time means high variance.
"Share Rate" is simply 2^32 * "DiffE" / "«Elapsed" - where "DiffE" is the Diff submitted during "«Elapsed" - but not shown there.

Everything on that page but "Hash Rate" is accurate to a fraction of a second - as soon as KDB knows about a share, which usually takes microseconds after it arrives at the main pool node, it's there on the page.

Kano, that's for answering these questions.

Would an additional help section of the website for definitions be too far down the backlog of work to do?

Thanks as always!!

[jhoren]

So my ping to west coast is 56.* and my ping to east coast is 57.*

Sounds like you should set one of them as pool 1 and the other as pool 2.

Already been done.

[userghost]

Ok so I deposited some money on NH I was going to send some extra power to this pool, I can't get it to work though, NH can't seem to connect to this pool on any port. Is there a reason for this?

Several months ago (last year?) when the pool was last this size a lot of it was rental and it turned out a large percentage of that rental hash was either maliciously or unintentionally returning very low quality hash results. Ergo all rental has since been banned from here.

I figured it out. I'm renting 1.3ph for 12 hours and pointing here.

[BSGMiner]

So my ping to west coast is 56.* and my ping to east coast is 57.*

Sounds like you should set one of them as pool 1 and the other as pool 2.

Already been done.

Then, kick back and MINE ON!!!

[clgrissom3]

Ok so I deposited some money on NH I was going to send some extra power to this pool, I can't get it to work though, NH can't seem to connect to this pool on any port. Is there a reason for this?

Several months ago (last year?) when the pool was last this size a lot of it was rental and it turned out a large percentage of that rental hash was either maliciously or unintentionally returning very low quality hash results. Ergo all rental has since been banned from here.

I figured it out. I'm renting 1.3ph for 12 hours and pointing here.

We've been through the crappy hash that comes from NH & WH before.  I for one would prefer that you don't use it here on the Kano pool.  Kano has said he is blocking all rental hash so if you found a way to bypass it I'm sure he will have something to say about it one way or another.

[userghost]

Ok so I deposited some money on NH I was going to send some extra power to this pool, I can't get it to work though, NH can't seem to connect to this pool on any port. Is there a reason for this?

Several months ago (last year?) when the pool was last this size a lot of it was rental and it turned out a large percentage of that rental hash was either maliciously or unintentionally returning very low quality hash results. Ergo all rental has since been banned from here.

I figured it out. I'm renting 1.3ph for 12 hours and pointing here.

We've been through the crappy hash that comes from NH & WH before.  I for one would prefer that you don't use it here on the Kano pool.  Kano has said he is blocking all rental hash so if you found a way to bypass it I'm sure he will have something to say about it one way or another.

I'll be more than happy to tell him what I'm doing if he inquires. Not trying to cause any problems, just figured the more hash the better. Should shorten my ramp up time for my normal hash rate as well. Not using NH or WH though

[clgrissom3]

Ok so I deposited some money on NH I was going to send some extra power to this pool, I can't get it to work though, NH can't seem to connect to this pool on any port. Is there a reason for this?

Several months ago (last year?) when the pool was last this size a lot of it was rental and it turned out a large percentage of that rental hash was either maliciously or unintentionally returning very low quality hash results. Ergo all rental has since been banned from here.

I figured it out. I'm renting 1.3ph for 12 hours and pointing here.

We've been through the crappy hash that comes from NH & WH before.  I for one would prefer that you don't use it here on the Kano pool.  Kano has said he is blocking all rental hash so if you found a way to bypass it I'm sure he will have something to say about it one way or another.

I'll be more than happy to tell him what I'm doing if he inquires. Not trying to cause any problems, just figured the more hash the better. Should shorten my ramp up time for my normal hash rate as well. Not using NH or WH though

Interesting...it seemed when you posted "I deposited some money on NH I was going to send some extra power to this pool" that it was NH.

Rented hash just about killed this pool not too long ago.  I even had a routine where I rented about 200TH and rolled the payouts back in continuously.  I lost money over time and gave it up.

[ccgllc]

So my ping to west coast is 56.* and my ping to east coast is 57.*

Sounds like you should set one of them as pool 1 and the other as pool 2.

Also sounds like U r in St. Louis  

You made me curious.  From a server I have access to near St. Louis (Ofallon, Mo.)

Stratum.kano.is averages about 67ms
Nya.kano.is averages about 52ms

[userghost]

Ok so I deposited some money on NH I was going to send some extra power to this pool, I can't get it to work though, NH can't seem to connect to this pool on any port. Is there a reason for this?

Several months ago (last year?) when the pool was last this size a lot of it was rental and it turned out a large percentage of that rental hash was either maliciously or unintentionally returning very low quality hash results. Ergo all rental has since been banned from here.

I figured it out. I'm renting 1.3ph for 12 hours and pointing here.

We've been through the crappy hash that comes from NH & WH before.  I for one would prefer that you don't use it here on the Kano pool.  Kano has said he is blocking all rental hash so if you found a way to bypass it I'm sure he will have something to say about it one way or another.

I'll be more than happy to tell him what I'm doing if he inquires. Not trying to cause any problems, just figured the more hash the better. Should shorten my ramp up time for my normal hash rate as well. Not using NH or WH though

Interesting...it seemed when you posted "I deposited some money on NH I was going to send some extra power to this pool" that it was NH.

Rented hash just about killed this pool not too long ago.  I even had a routine where I rented about 200TH and rolled the payouts back in continuously.  I lost money over time and gave it up.

It was nicehash originally but it didn't work. I found a different rental service that was compatible. So I xfered my money to x site and started hashing!