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

I'll weigh in on this one.

The per block payout is probably my biggest 'dislike' regarding mining here on this pool.

For me -- I don't "spend" the bitcoin often -- and then, when I do, it takes forever for my trezor to compile all of the tiny transactions to make up however many btc I'm trying spend.  If the amount is over 4btc -- it won't even work due to the size.  Also, the transaction fees are horrendous.

Having said that -- I get kano's perspective that he isn't a bank.

Just one of those quirky things I guess about this pool.

As an aside -- I just recently changed my payout address from my trezor to a coinbase wallet -- and I'll aggregate there without the fees.  The thing I don't like about this plan, is that it is coinbase (with their kyc rules).  Does anyone else know of an online wallet that one can aggregate micro transactions -- and then occasionally pull them into cold storage anonymously and fee free?

Sorry, but do you have multiple personality disorder today? That first paragraph first agrees with larger payments, then the second part disagrees with larger payments, because larger consolidated payments mean the pool operator running a wallet that holds those payments until they are ready to payout.

So do you agree with one large consolidated payment a day or not? I think for this pool it works fine without, all you need to do is have a mining wallet and a cold, or spending wallet, the mining income goes into the mining wallet, and every week or so you send the coins from your mining wallet into your cold wallet, which consolidates the dust for you. Then when you want to trade or buy something with your coin you do so from the cold/spending wallet and, if you use a reasonable sized transaction fee, that spend will go through alot faster than if you sent it from your mining wallet.

Agreed. I do not see any point for it, other than extreme insecurity perhaps. If one does not trust the pool operator to reasonably protect/hold the rewards until adequately verified, one should probably mine elsewhere...methinks. Additionally, it puts the miners' accounting load on Kano, where it doesn't belong...again, methinks.

But then, I've been occasionally told I think too much...methinks. 

"engineers are not good at dealing with customers..."
....typically.

kano needs a hand holding rep...at some point or even better, ask someone to design it into his front page-i am sure that there are tons of freelancers who could do it. With a good front page, this pool can triple (at least) in size.

the following explains it better:
https://youtu.be/hNuu9CpdjIo?t=10

I woke up to see we had a 2 block night.

 so it would be really great if we also have a 2 block day, today. ;-)

Thanks Kano!

Even this quick description is super helpful.
Personally, a lot of the abbreviations were tripping me up (e.g., 5Nd). So maybe just typing them out on your homepage would help?
The quick math examples were also super helpful to make things concrete and real.
Your explanation here makes it much more clear why there is "ramp up" time for me just plugging in my miner, and with this understanding, a new person may be more willing to stick around.
I know there are tons of resources and wikis, but just a suggestion to take some of what you just typed and include it on the homepage of kano.is to make it easy/clear for people to stick around.

Sweet!  Waking up to another 2 block day!

Well I just went to bed and got the 'magic bells' as I lay down so took me a bit to get up and turn on my screens

Block!

Kano, you beat me to it by 7 seconds!

Block! by btsgold
2.2BTC txn fees
Prolly an S7

Nice to wake up and have one in the basket!

Well that's a technicality that isn't an understanding issue
OK then it should read

That 'technicality' is described quite clearly at the bottom of the payouts page.
(and every pool has a 'technicality' of rewards->pay)

Thoughts on an adjusted version of this:

Every time we find a block: 1. Rewards for recently matured (unpaid) blocks are released, 2. You earn rewards for your accepted shares for a certain amount up to when the block was found.

I also thought it's a good time to send a reminder plug for Zach's monitor.
All newbies should take a look at it for a different perspective for kano.is published stats and as a supplemental tool as mentioned in the OP.

Block! by canaan
and 4 payouts
A7v2

That is a really good way to explain all of that...

Well the pool is PPLNS, like the majority of non-PPS pools, so I guess then the problem might be that people don't understand PPLNS, even including the description I give on the web site

I'll give another version and then feel free to tell me what doesn't make sense.

Every time we find a block, we pay the shares for a certain amount up to when the block was found.
That's the 'N' in PPLNS

Bitcoin has a difficulty for finding blocks called the Network Difficulty (I abbreviated it as Nd)

It's currently ~461 Billion
5Nd = 5 times Nd = ~2.3Trillion

Every share you submit to the pool has a difficulty that the pool requires - you see that in your miner and on the web site workers.
Usually around 1,000 to 20,000 - if yours are much lower then you are basically mining for fun so none of this really matters.
That's 'Diff'

So the pool adds up all those shares for the last ~2.3Trillion Diff and pays everyone their ratio of that 2.3Trillion as part of the 12.5+ BTC block.
So if you found 2.3Billion worth of shares, you'd get ~1,000th of the miner reward.

--

Now the following is the same for all pools that don't hide information

When we find a block, the pool has kept track of how much work was done (total valid Diff submitted to the pool) since the last block was found.
It's expected, on average, to be Nd, so if the work done was exactly Nd, then the block Diff% would be 100%
Block finding is random.
So it could be twice as much work as expected, so 200%, or it could be half as much work as expected, so 50% ... or any other %
Luck% is just Diff% upside down (1 / Diff%)

ref http://en.bitcoinwiki.org/Main_Page
https://en.bitcoin.it/wiki/Bitcoin

Hey Kano (And all)

 Brand new to mining and opted for your KanoPool due to all the great things I've read in the forums.

 Some unsolicited feedback: I've seen a lot of comments about new miners joining and leaving Kano due to the spikes in blocks found.

 Personally, I think what might help is more of a laymen's term explanation of how the pool works on the main Kano.is page. I've read it and re-read it 10 times, and still don't completely understand the 5Nd thing. Also, some of the stats on the stats page confuse me (e.g., Diff, Diff%, etc.)

 I know Kano does plenty already, but maybe some of the people smarter than me could crowd source a more basic explanation for the pool? This could help attract / retain new people? Let me know if I can help!

 Orrrrr feel free to completely ignore this.

Thanks!

Shifts appear, are created, ~13 minutes after they finish.
The start isn't the unknown factor, it's the finish point that it has to wait until all the workinfo is complete/confirmed then it works out the shift.

Edit: and you can see that the shifts are all OK by the fact they all have a Start and Length, so the start of any following shift will be Start+Length

The Server time doesn't affect the web display at all, it uses UTC for all displayed time since people all over the planet look at it.
Internally, CKDB treats everything as UTC and the code all deals with converting the Postgresql dates to and from UTC.

Each web page, at the bottom right in small letters, shows what your browser thinks is your local time, and at the bottom left, what the server thinks is UTC time.
That also effectively shows any discrepancy between your computer and the actual time, after you subtract the network and processing delay for the page request.

Maybe so, but if a computer is set to UTC, then there is per definition no daylight saving.