Pages:
Author

Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 100. (Read 5352527 times)

legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
just started with kano pool almost 48 hours ago with just 1 of my miners to test the waters - we hit a block after around 70 hours, as I was not there for all the shifts I expect that is why my payout was so low - in other pools this one miner would have made 10x the amount in 2 days. I am hoping that with participation in all the shifts for the next block that I will earn a higher reward to make it worthwhile. If I do well enough here, I will bring my other asics over.

anyways, I just wanted to say hello and hoping this pool works out good for me!
Yep the thing to remember is the PPLNS here N=5Nd

That's also explained on Help->Payouts on the web site.

The most relevant part to your 'hope' is:
"The 5Nd means it takes that long to reward your shares.
The ramp isn't missing rewards, it's delaying them to reduce variance.
Each share is rewarded in all the blocks found in the 5Nd after the share."

So when you stop mining you will still have rewards due in the 5Nd of blocks after you stop.

This diagram might also help:
https://bitcointalksearch.org/topic/m.26608107
legendary
Activity: 2324
Merit: 2533
EIN: 82-3893490
just started with kano pool almost 48 hours ago with just 1 of my miners to test the waters - we hit a block after around 70 hours, as I was not there for all the shifts I expect that is why my payout was so low - in other pools this one miner would have made 10x the amount in 2 days. I am hoping that with participation in all the shifts for the next block that I will earn a higher reward to make it worthwhile. If I do well enough here, I will bring my other asics over.

anyways, I just wanted to say hello and hoping this pool works out good for me!
member
Activity: 490
Merit: 16
1xA921 + 1xA741 + Backup-->1xA6 ;)
Done at 01:00:01 UTC

All NYA miners have switched to the new node now.
Great work, great pool!
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
As I mentioned in Discord ... Smiley

The NYA node has still been showing a lot of disconnects since the provider did maintenance on it.
So I've created a new NYA node with a different provider.

nya.kano.is now points to the new node

This wont affect any mining other than: if your miner disconnects from NYA and reconnects, it will connect to the new NYA node.


However, to add to that:
I'll force a failover to the new node in about a day if miners are still pointed at the old node.
This will simply be to stop the old node accepting miners and then everyone still on the old node will reconnect to the new node.

Mine on! Smiley
So far there's only been a few % of workers that have reconnected to the new node, a lot less than I expected after the number of times it was showing miners disconnecting the other day.

Anyway, at 01:00 UTC (in a bit over 13.5 hours) I'll push everyone left on the old node over to the new node.
There's nothing for anyone to do, it will just be a failover off the old node for miners still pointing to the old NYA node and failback immediately to the new NYA node.
Of course, any miners already switched to the new NYA node will just continue mining uninterrupted.

Everyone else will be unaffected.
Done at 01:00:01 UTC

All NYA miners have switched to the new node now.

Mine on! Smiley
jr. member
Activity: 119
Merit: 2
I've been getting a blank page stating "Too many accesses please try again later"

It's been that way for about 2-3 hours now.

Account is Luggyman.

is this to be expected? Front end down?

I wasn't refreshing like crazy or anything like that.

Thanks!
The problem was trying to change your payout address multiple times.
That ban cuts in pretty quickly.
Ban cleared.

Gotcha. Thanks man!
newbie
Activity: 2
Merit: 0
In case you didn't see it in Kano's post, this is the calculator to use... http://tradebtc.net/bitcalc.php

The daily expected bitcoins for 210PH/s is 7.38273408 and divide that by 12.5 gives us 0.59 Blocks/day.  That is roughly a block expected every 2 days (1.69 days) at the current diff and pool hashrate.  We are well ahead of this pace for September.

yea, i saw that, but it would be nice to see that expectation on the top of pool here:
Last    Block
Pool:     53m (543172) (Expected: 42 hours)

I always expect the next block to be found within the next 10 Minutes.... ;-)

there is plenty of information on the site to make an educated guess... and the number will always be wrong...
member
Activity: 159
Merit: 12
In case you didn't see it in Kano's post, this is the calculator to use... http://tradebtc.net/bitcalc.php

The daily expected bitcoins for 210PH/s is 7.38273408 and divide that by 12.5 gives us 0.59 Blocks/day.  That is roughly a block expected every 2 days (1.69 days) at the current diff and pool hashrate.  We are well ahead of this pace for September.

yea, i saw that, but it would be nice to see that expectation on the top of pool here:
Last    Block
Pool:     53m (543172) (Expected: 42 hours)
hero member
Activity: 1610
Merit: 538
I'm in BTC XTC
Woot!  BlockBadger hits one, and I'm just about to head out to Wisconsin for a long weekend, so actually double WOOT!!  Cheesy Cheesy
Mine ON!!  Cool
jr. member
Activity: 61
Merit: 2
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
Block by BlockBadger! The blocks just keep coming! Cheesy

This is our 1st of BLOCK WEDNESDAY! Cheesy
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
As per the Help->Luck page, 1 in 2.7 blocks are 'expected', on average, to be over 100%, but currently 1 in the last 13 is pretty good Smiley
or even 2 in the last 18 - both stats including the current un-found block.

do you have somewhere calculation on the expected block time under current Difficulty and Pool Hashrate?

In case you didn't see it in Kano's post, this is the calculator to use... http://tradebtc.net/bitcalc.php

The daily expected bitcoins for 210PH/s is 7.38273408 and divide that by 12.5 gives us 0.59 Blocks/day.  That is roughly a block expected every 2 days (1.69 days) at the current diff and pool hashrate.  We are well ahead of this pace for September.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
As I mentioned in Discord ... Smiley

The NYA node has still been showing a lot of disconnects since the provider did maintenance on it.
So I've created a new NYA node with a different provider.

nya.kano.is now points to the new node

This wont affect any mining other than: if your miner disconnects from NYA and reconnects, it will connect to the new NYA node.


However, to add to that:
I'll force a failover to the new node in about a day if miners are still pointed at the old node.
This will simply be to stop the old node accepting miners and then everyone still on the old node will reconnect to the new node.

Mine on! Smiley
So far there's only been a few % of workers that have reconnected to the new node, a lot less than I expected after the number of times it was showing miners disconnecting the other day.

Anyway, at 01:00 UTC (in a bit over 13.5 hours) I'll push everyone left on the old node over to the new node.
There's nothing for anyone to do, it will just be a failover off the old node for miners still pointing to the old NYA node and failback immediately to the new NYA node.
Of course, any miners already switched to the new NYA node will just continue mining uninterrupted.

Everyone else will be unaffected.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
As per the Help->Luck page, 1 in 2.7 blocks are 'expected', on average, to be over 100%, but currently 1 in the last 13 is pretty good Smiley
or even 2 in the last 18 - both stats including the current un-found block.

do you have somewhere calculation on the expected block time under current Difficulty and Pool Hashrate?
Time doesn't matter as long as we are finding enough blocks per diff change.
However, Help->Payouts mentions how long 5Nd is which is, of course 500%
And then of course there's also http://tradebtc.net/bitcalc.php
hero member
Activity: 1063
Merit: 502
RIP: S5, A faithful device long time
Um, yeah so why is the pool showing a hash rate of 405,245.59THs presently when the normal is around 200K?  Thanks. 

I point 200 Ph/s on kano pool if I can get money somewhere. Then hash rate gonna be over 200 Ph/s. 400 Ph/s
member
Activity: 159
Merit: 12
As per the Help->Luck page, 1 in 2.7 blocks are 'expected', on average, to be over 100%, but currently 1 in the last 13 is pretty good Smiley
or even 2 in the last 18 - both stats including the current un-found block.

do you have somewhere calculation on the expected block time under current Difficulty and Pool Hashrate?
member
Activity: 434
Merit: 30
i didn't want to complain... Its just that we were so well on route with those bright green's, its a bit disappointing again to get back to "regular" values of luck... Added that there's extra help due a failover setting of someone, one would think this block be'd cracked sooner.. (i know, not the whole 54hrs, but it should help, right?)
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
As I mentioned in Discord ... Smiley

The NYA node has still been showing a lot of disconnects since the provider did maintenance on it.
So I've created a new NYA node with a different provider.

nya.kano.is now points to the new node

This wont affect any mining other than: if your miner disconnects from NYA and reconnects, it will connect to the new NYA node.


However, to add to that:
I'll force a failover to the new node in about a day if miners are still pointed at the old node.
This will simply be to stop the old node accepting miners and then everyone still on the old node will reconnect to the new node.

Mine on! Smiley
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
then it's good news! it's already 408 PH Shocked  waiting for a block  Grin

yeah... 54hours already.... Even with +400Ph...


crack that bock!!! Shocked
It's not 54 hours at 400PH Tongue

It's simply a block over 100% so far ... which is typically 'expected' way more often than has happened for the last 8 days.

As per the Help->Luck page, 1 in 2.7 blocks are 'expected', on average, to be over 100%, but currently 1 in the last 13 is pretty good Smiley
or even 2 in the last 18 - both stats including the current un-found block.

Yea, we seriously have nothing to complain about...we have been enjoying crazy good luck this month! Cheesy
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
then it's good news! it's already 408 PH Shocked  waiting for a block  Grin

yeah... 54hours already.... Even with +400Ph...


crack that bock!!! Shocked
It's not 54 hours at 400PH Tongue

It's simply a block over 100% so far ... which is typically 'expected' way more often than has happened for the last 8 days.

As per the Help->Luck page, 1 in 2.7 blocks are 'expected', on average, to be over 100%, but currently 1 in the last 13 is pretty good Smiley
or even 2 in the last 18 - both stats including the current un-found block.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
I've been getting a blank page stating "Too many accesses please try again later"

It's been that way for about 2-3 hours now.

Account is Luggyman.

is this to be expected? Front end down?

I wasn't refreshing like crazy or anything like that.

Thanks!
The problem was trying to change your payout address multiple times.
That ban cuts in pretty quickly.
Ban cleared.
Pages:
Jump to: