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

Block by blockoperations!  That is his 2nd Kano Block and our 3rd of the day! 

You get the firmware update yet? Not getting any response from support.
EDIT: Hey they just kicked it out.

EDIT#2
bitcoin still not visible on keepkey with new beta. Oops.

cytline bitches!!  Woo hoo!! 

GREEN STAR to Cytline!!!

common blocks.... we need a quick back to back blocks.... ooom!

Block by cytline!  That is Kano block #16 for him and our 2nd of the day!  

Patience is a Virtue.... the elusive block will come soon... oooom!

The bottom is about to DROP out of this storm of Blocks!

Just pointed an additional sp20, s7 and s5 at kano 

Thanks for the reply! I will have patience and see what happens. Will take your advice and make individual usernames for the miners. Just want to get the basics down first

Dig DEEP! We need at least three more blocks for today!!!

GREEN STAR to the next BLOCK FINDER!! 

We're fixin' to...



...mine some blocks!

You won't receive a payout of accumulated block rewards (confirmed) until the next block is found. The rewards get queued up, and release upon the next block find, so long as Kano's had a chance to review it, etc. A suggestion...if you are really into tracking if a given machine is producing, establish a user account with separate workers. And...I may be wrong, but I don't think the "number of shares" in the data line is what's waiting to disburse.

Thank you for the reply! I can tell this is a great comunity to start my mining adventure in! I have been online for a few days and although blocks I have been a part of says they are matured I have not seen a payout yet. When I check https://kano.is/address.php?a=18kbxaVRW7bUzvA8qxRCQgdfhUtUniC2EL the shares just keep going up. Will those go down when a payment has occured?

Sorry again for the noob questions! Just trying to get all in order until my equipment arrives!

+1 on Python's idiotic reliance on indentation for delineating code blocks. Makes it a pain to copy and insert code from other developers because some (the right thinking ones) use tabs and others (the wrong thinking ones) use spaces. Yeah, I come down on the tab side in that religious war

What's wrong with using explicit characters, like braces, for code blocks for crap's sake?

But even with pain in the ass of having to entab and normalize text more often than I'd like, I find Python too damn useful for small scale needs. It's great for limited scripts and glue between other tools. More often than not I start writing what I thought would be a simple script in Bash, then I get over some number lines or need to do anything complex then wish I'd used Python.

That said I'm glad you're not using Python for this pool. I assume that it's all compiled C, and it shows.

I recently started running a proxy and it's really interesting what you see in the logs. Kano.is and the ck solo pool are both rock solid on the connection front. Literally zero disconnects.

F2Pool (which I have as a third backup) shows something like 40 disconnects a day. Some other pools that I won't mention seem similarly shaky.

Running a proxy has been very eye opening...

I haven't look at it, and I can't stand a language that decides code execution based on invisible characters ... so I avoid python completely ... and no that's not a complaint about your code Just thought I'd mention that

However, to know something of the statistics of workers ...
To know that a worker has stopped is quite simple:
If it hasn't sent a share for 1 minute

1 minute is the best choice

The stats work as follows:
A worker is expected to send 18 shares per minute = 1 share per 3.3333 seconds.

Shares are like blocks, they follow the same poisson distribution of course since blocks are shares
So 30 seconds for a share, would be like a 30/3.3333 = 900% block.
However, of course, you find WAY more shares than blocks.

We expect, on average, a >900% share once every 8103.1 shares.
But since shares come in WAY more often than blocks
(18 * 60 * 24) / 8103.1 gives about 3.2 times a day, a 30 second check would fail and say the worker is down.

At one minute, would be 60/3.3333 = >1800% share = on average, once every 65,659,969 shares
i.e. about once every ... 2533 days ... or about once every ~7 years

So going from 30 seconds to only 60 seconds makes the test exceptionally unlikely to be wrong.
So yep, a VERY reliable test on a worker (if it has only one miner) is that it hasn't submitted a share for 60 seconds.
The API provides the time of the API request and the time of the last share.
Of course you also need to handle when the API isn't working when I do a CKDB restart
Edit: and of course the cgminer API has this same information.

...

of course, don't forget that if you had 2533 miners, you'd expect, on average, one each day to fail the 1 minute test.
Go to 2 minutes and then, yeah, you'd need all the miners on the planet to fail a 2 minute test.
(Edit: 2 minutes is one in ... 4.5x10^14 shares)

To Kranium!

Block by kranium with his 10th Kano block!  This is our 1st block just an hour into the new day!  

This is a nice fat block also! 

Okay, Guys and Gals, lets get this block party Monday ROLLING!
A GREEN star to the next block finder!!

Come on down BLOCKSSSSSSSSSSSSSSSS!

Baby needs new shoes!! 

Assuming you read this:  https://kano.is/index.php?k=payout

After a block has matured (reached 101 confirmations) it is queued for payout and sent out upon the next block the pool finds. Kano does sleep and sometimes it takes a bit longer if the blocks come fast and furious.