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

Moo!

You never will, muhahahaha!

Ditto here on the full node thingy...I generally run around 65-90 connections. Not my forte for understanding, but anything if it can help.

Hi, i have been mining in this pool for almost 3 days but i didn't get paid !
i can see my worker and the hash rate all is ok so when i'll get paid ?
i'm using Antminer s9

Well, procrastinating (lazy-ass) me has finally switched all of my miners to the NY node. I have intended to do it since its inception, but..... I never bothered to check the ping times. I'm in IT, BTW, so I should know better...

I'm located in Western North Carolina, so it shouldn't be rocket science for me to use the NYA node.
Anyway, here are my results:

C:\WINDOWS\system32>ping stratum.kano.is

Pinging stratum.kano.is [45.76.68.6] with 32 bytes of data:
Reply from 45.76.68.6: bytes=32 time=82ms TTL=47
Reply from 45.76.68.6: bytes=32 time=79ms TTL=47
Reply from 45.76.68.6: bytes=32 time=95ms TTL=47
Reply from 45.76.68.6: bytes=32 time=79ms TTL=47

Ping statistics for 45.76.68.6:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 79ms, Maximum = 95ms, Average = 83ms
~~~~~~~~~~~~~~

C:\WINDOWS\system32>ping nya.kano.is

Pinging nya.kano.is [104.207.132.42] with 32 bytes of data:
Reply from 104.207.132.42: bytes=32 time=51ms TTL=46
Reply from 104.207.132.42: bytes=32 time=32ms TTL=46
Reply from 104.207.132.42: bytes=32 time=99ms TTL=46
Reply from 104.207.132.42: bytes=32 time=35ms TTL=46

Ping statistics for 104.207.132.42:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 32ms, Maximum = 99ms, Average = 54ms
~~~~~~~~~~~~~

Additionally, a note to @Kano. I know someone has previously offered to add the Kano info to their full node. I don't recall if there was an answer.
I have been running a full node for about a year and I would gladly add the Kano ID/IP to my node if it would help with our block propagation. I usually have about 50 good peers on my node.

If there is any interest, Kano, please feel free to PM me in response. Thanks!

COMEONBLOCKSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!  

If we don't hit three blocks by Wednesday I told the wife we are sacrificing the cow!   Kids cried...............BTC

Thanks Kano. Mine On, I look forward to adding a little Hash to the Pool!!

The Best,
Tim

http://bfy.tw/Ekpm

...
Google 'ping network' perhaps? I head it's a newfangled thing called a search engine....

....yea i dont know how to do that 

Best bet is to ping and see if its got less latency

should i use this node also ( nya.kano.is) ?
since i am in the New York area?

First off, thanks, Kano.

Second, damn man. I've been mining for a while now and all these new miners showing up with more hash power than myself, sigh. LOL. If Bitmain would ACTUALLY SELL SOME MINERS! That and I had to pay off a debt so now we need to seriously start find blocks while the pool is at 60PH cause I get a lot more than I did when it was way higher.

And if Caanan would ship my Avalon, I could add 7 more TH or whatever speed they are . Better than nothing.

this answered so many questions
thanks Kanosan (bow)

Your closest node should be nya.kano.is (instead of stratum.kano.is)
You can ping them to verify it, but considering your location, it should be nya.kano.is by a pretty good margin.

As for your first backup, it should be stratum.kano.is
Although stratum.kano.is and nl.kano.is should give you similar pings, it's much better to use stratum.kano.is in your case.

The shares you submit (and blocks you find) depend on how close you are to any closest node - that's what decides how quickly they can be processed, so that's why you use nya.kano.is as the first pool.

However, the work change currently depends on the full path back to the US west coast (ish), so you want to minimise both together as much as possible.
When comparing 2 nodes that are similar, then you use the one closest to US west coast (ish), and since stratum.kano.is is US west coast, it's preferable when choosing between nl.kano.is and stratum.kano.is as the backup pool.

Kano - I am new to the mining scene. I expect 4 S9 14 TH/s to be delivered between Dec 1 and Dec 10. I live in the Northern Virginia Area and have 1GB/s up and Down fober connection to the Internet. What settings should I use when setting up these miners to point them to Kano Pool? Sorry if I sound stupid, just a Newbie and want to be with Kano Pool since it is the pool that most reflects what Bitcoin Mining should be all about.

Thanks - Tim

Kano, I just added 2 brand spankin new S9's with 14 TH each! Woot woot! One  averaging 14.80 and the other is like 14.140!   But I had to take of the shelf the 2 s7's which were hustling like Rick Ross for me for like a year!  Besides, one of them was the reason why my name is on acclaim board!  So sad to see him go 

Kano.
What an amazing answer to what must be a fairly mundane question from myself !

I can see why your pool gets good reviews for tight comunity here.

Thank you for the clarity.
Im likely going to hold out for the big wins to help make up for the recent dip.
But i can see how some operations could be burried by these dips.

-Andy

Basically there are 2 main factors in mining:

1) Variance
2) Fees

Firstly PPS:

Mining on a PPS pool has almost no variance.
You get rewarded exactly for the shares you submit, thus the only (tiny) variance is just the share finding variance of your miners.
Thus if you were mining PPS on AntPool you would have seen a very small variance in your daily reward, i.e. it wouldn't have been exactly the same every day, but close enough.

However, block finding on bitcoin has quite obvious variance.
There isn't a block found every 10 minutes on the bitcoin network, that's just the average expected time for a block on the network.
You'll see blocks found a few seconds apart sometimes, or a few minutes, or even over an hour or more apart.

So lets say, PPSPool gets a 75% Diff block followed by a 150% Diff block - variance
They can pay everyone after the 75% block, because PPSPool earned more than they have to pay the miners - they earned a full block (100%) but only have to pay the equivalent of 75% worth of shares the miners sent to the pool.
But once the 150% block arrives, they have 225% total shares from miners, but only 2 blocks (200%) to pay them with.
Ouch they now have lost 25% of their stash

So to handle this problem, they must do 2 things:
1) Keep a safety net of BTC to be able to pay everyone when luck is worse than 100%
2) charge a higher fee to cover that risk of bad luck.

There's a paper all about this here which includes the risks of mining on low fee PPS pools:
http://arxiv.org/pdf/1112.4980v1.pdf

One more important thing to know about all this is transaction fees.

When anyone finds a block, they don't (usually) just get the block reward (currently 12.5 BTC) but they also get all the transaction fees from all the transactions they include in the block.

This has actually been quite a lot of BTC for a while now - currently this month it's averaged about 7.5% more added to the 12.5 BTC of each block.

So this is where the pool fees make a VERY big difference in the equation.

If a PPS pool is paying it's miners 100% PPS - then the pool is charging the miners, on average, for this month, 7.5/(100+7.5) = a 6.98% fee.
Wow that's even higher than the ridiculous fees at nicehash

In the case of last June, tx fees average for that month was 22.3%, so a 100% PPS pool was charging everyone 22.3/(100+22.3) = a huge 18.2% fee

Some PPS pools pay their miners less than 100% PPS, others pay a bit more than 100% PPS
You'd have to check the PPS pools to see what their fees are from week to week and month to month.

Now PPLNS:

On PPLNS, we reward all miners every time we find a block.

This means that when we are lucky and find more blocks than expected, we are rewarding miners better than expected.
But when we are unlucky and find less blocks than expected, we are rewarding miners worse than expected.

So what does 'expected' mean?
It's what you would 'expect' to get if the pool luck was always 100% (which of course it isn't)

So what is the 'expected' reward on PPLNS?

That again depends on the PPLNS pool's fees.
Here the fee is 0.9% of the total and we include Txn fees.
So if luck was 100%, then the pool's average PPS for a month would be (100%+Txn) * 0.991

But there's the issue of luck/variance to consider.
You wont get the same reward every day, some days you'll get more than you expect and other days less, and at the worst, some days no reward at all.

FYI: AntPool PPLNS keeps the txn fees - so this month they would be charging you a 6.98% fee (ouch)
Last June they would have been charging you a 18.2% fee OMFG!

So how do you 'expect' to be better off here?
Well you expect to be better off in the long run, since the fees here are lower than any other pool worth mining on.

However, sometimes the luck sux and you get paid a lot less, other times the luck is good and you get paid a lot more.
In the long run it averages out - as the Blocks web page history information shows.

It's just a question of how close to a profit or loss your mining is.
If you can deal with getting 70% PPS in a month on rare occasions, without going broke, then you should be OK here.
If you can deal with getting 162% PPS in a month here on rare occasions, then that should be OK also

Some large blocks with good rewards are being found today    Hope 1 or 3 has our name on them    I'm feeling lucky today