Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 870. (Read 5352367 times)
August 14, 2017, 02:45:17 AM
500%? hmm.... getting a bit nervous..... what is going on?
August 14, 2017, 01:18:43 AM
The pool is about to rip a bunch of blocks.
I can feel them getting ready to pop
I can feel them getting ready to pop
I can feel it too! When we don't find a block for a while like now they usually start popping like popcorn!
. And Kano, thanks for the payouts! I really needed them! 
August 13, 2017, 11:55:41 PM
I lost my cable service (Internet, phone, TV) at 1400 HST yesterday when one of Spectrum's crews in the neighborhood was supposed to terminate service on unit 8C in the state-owned housing next door...but they didn't verify their addresses, and instead unplugged MY unit, which is also 8C, but at a different street number. Spectrum at least...after a couple of hairy phone calls...admitted their error and got a tech out here on OT (it's Sunday here) to hook it back up. 24 hrs down.
Turns out I didn't miss much, eh? Mine on...
Turns out I didn't miss much, eh? Mine on...
August 13, 2017, 10:58:27 PM
more than 60 hours, no block... what a bad luck 
Yup, this happens every now and then.
August 13, 2017, 10:55:22 PM
more than 60 hours, no block... what a bad luck
August 13, 2017, 08:07:55 PM
Quote
You expecting BTC to crash some time soon?
I never know! I like to trade on the exchanges when I am not at work as a hobby, so every little bit helps.
August 13, 2017, 07:09:45 PM
The last block churning over days was when my S3's arrived. This time I just turned on my S9 first time and block goes for days again. Great luck
August 13, 2017, 07:08:08 PM
It's brilliantly interesting to see how statistics (luck) work in real life at kano ;-)
oh btw, kudos to the guy running it all...
now feels like a good time to hit a few good home runs!
oh btw, kudos to the guy running it all...
now feels like a good time to hit a few good home runs!
Yeah, I just wish it did it at a time when BTC wasn't hitting record highs
Long term thinking is key
August 13, 2017, 07:04:34 PM
It's brilliantly interesting to see how statistics (luck) work in real life at kano ;-)
oh btw, kudos to the guy running it all...
now feels like a good time to hit a few good home runs!
oh btw, kudos to the guy running it all...
now feels like a good time to hit a few good home runs!
Yeah, I just wish it did it at a time when BTC wasn't hitting record highs
August 13, 2017, 06:32:45 PM
It's brilliantly interesting to see how statistics (luck) work in real life at kano ;-)
oh btw, kudos to the guy running it all...
now feels like a good time to hit a few good home runs!
oh btw, kudos to the guy running it all...
now feels like a good time to hit a few good home runs!
Yeah, I just wish it did it at a time when BTC wasn't hitting record highs
August 13, 2017, 04:10:53 PM
Thought I would share this for those that try to understand Kano pools accounting and why some of us like it.
I downloaded my bitcoin transactions and ran a simple spread sheet calculation.
I currently run 2 S9 miners, one of which is only operating at 2/3 as one of its hashing boards is not working.
That gives me a hashing number of 13.6 + 9.2 or 22.8TH/s
For the last 14 days the average total payout per day is 0.007548879285714 bitcoin
each individual payment is between .0039 and .0035 bitcoin
On some days I get 1, or 2, or 3 or maybe even 4 payments. On some days I may get no payments, depending on if the pool finds a block.
The reason the payments vary is due to Kano including the transaction fees collected for block creation and those transaction fees change depending on
factors outside of Kano's control. The blocks found can vary between 12.5 up to and even past 16 bitcoin.
Most "other" poos, er pools, keep that 0 to 3.5 bitcoin but Kano passes it on to us!
The average payment is higher than I would receive for any other pool currently operating.
This is why I stay with Kano.
If you get on Kano pool and mine it for a day or two there is a chance you will not receive any payments or a very low payment. This is due to the payments being divided into 5 roughly equal parts, that are then paid out over 5 payments. Once you have been mining long enough for 5 payments to have happened you will start to see the full amount of your mining on every payment. Payments happen when blocks are found, this means you may see payments right away, or may not see any in a 2 day period. I have seen kano pool find no blocks for over 48 hours and find 4 blocks in 12 hours. Kano provides extensive information on his web page showing what is happening.
Why am I promoting kano pool? Well, the more people that mine here the greater total hashing power. The greater hashing power the more blocks will be found. The more blocks found will keep payments flowing more regularly. I won't make any more money, since with more total hashing power you pay out to more people, but it would provide a more consistent flow of money.
If you wonder what I meant by more hashing power means more people but the same payout for me, look at it this way. If kano pool has 80PH/s each of my payouts is as stated above, about .0036-.0037. If hashing increased to 160PH/s, then my payouts would drop by about half, but I would get twice as many payouts in the same amount of time. This is because my percentage of hashing is not going to change, unless I buy more equipment. That means my percentage of hashing between a pool total of 80PH/s and 160PH/s would drop by about half, but, we would find more blocks, so I would get the same amount in the end.
I guess Kano would make more money, assuming he would not need to invest in more equipment and fixed costs to support a larger hashing base. I see that as a good thing because I like the way Kano does business.
dzimmerm
I downloaded my bitcoin transactions and ran a simple spread sheet calculation.
I currently run 2 S9 miners, one of which is only operating at 2/3 as one of its hashing boards is not working.
That gives me a hashing number of 13.6 + 9.2 or 22.8TH/s
For the last 14 days the average total payout per day is 0.007548879285714 bitcoin
each individual payment is between .0039 and .0035 bitcoin
On some days I get 1, or 2, or 3 or maybe even 4 payments. On some days I may get no payments, depending on if the pool finds a block.
The reason the payments vary is due to Kano including the transaction fees collected for block creation and those transaction fees change depending on
factors outside of Kano's control. The blocks found can vary between 12.5 up to and even past 16 bitcoin.
Most "other" poos, er pools, keep that 0 to 3.5 bitcoin but Kano passes it on to us!
The average payment is higher than I would receive for any other pool currently operating.
This is why I stay with Kano.
If you get on Kano pool and mine it for a day or two there is a chance you will not receive any payments or a very low payment. This is due to the payments being divided into 5 roughly equal parts, that are then paid out over 5 payments. Once you have been mining long enough for 5 payments to have happened you will start to see the full amount of your mining on every payment. Payments happen when blocks are found, this means you may see payments right away, or may not see any in a 2 day period. I have seen kano pool find no blocks for over 48 hours and find 4 blocks in 12 hours. Kano provides extensive information on his web page showing what is happening.
Why am I promoting kano pool? Well, the more people that mine here the greater total hashing power. The greater hashing power the more blocks will be found. The more blocks found will keep payments flowing more regularly. I won't make any more money, since with more total hashing power you pay out to more people, but it would provide a more consistent flow of money.
If you wonder what I meant by more hashing power means more people but the same payout for me, look at it this way. If kano pool has 80PH/s each of my payouts is as stated above, about .0036-.0037. If hashing increased to 160PH/s, then my payouts would drop by about half, but I would get twice as many payouts in the same amount of time. This is because my percentage of hashing is not going to change, unless I buy more equipment. That means my percentage of hashing between a pool total of 80PH/s and 160PH/s would drop by about half, but, we would find more blocks, so I would get the same amount in the end.
I guess Kano would make more money, assuming he would not need to invest in more equipment and fixed costs to support a larger hashing base. I see that as a good thing because I like the way Kano does business.
dzimmerm
I only run at ~19TH/s but fully support d's review above!
To add, by joining Kano you're joining a non-Chinese pool. This is good for the bitcoin community as a whole. So all things equal, join Kano!
August 13, 2017, 03:43:07 PM
It's brilliantly interesting to see how statistics (luck) work in real life at kano ;-)
oh btw, kudos to the guy running it all...
now feels like a good time to hit a few good home runs!
oh btw, kudos to the guy running it all...
now feels like a good time to hit a few good home runs!
August 13, 2017, 12:08:09 PM
Looks like Lady Luck is making us pay for that last run of blocks, lol...
Let's try good old Brute Force.
Cranking the miners up to 11 right now.
Release the Kraken!
Let's try good old Brute Force.
Cranking the miners up to 11 right now.
Release the Kraken!
August 13, 2017, 11:32:49 AM
popping blocks))
August 13, 2017, 10:20:30 AM
The pool is about to rip a bunch of blocks.
I can feel them getting ready to pop
I can feel them getting ready to pop
August 13, 2017, 06:58:44 AM
Curious:
does the pool's code matter in finding blocks? Is there a better pool code for finding more blocks? or is it the hashing power that matters?
Miners find blocks, pools provide work.does the pool's code matter in finding blocks? Is there a better pool code for finding more blocks? or is it the hashing power that matters?
Of course crappy code can mess that up in various ways, or even in some cases, bad code can fail to submit blocks ... multiple times .......
But in general, the pool code has little if no effect on the blocks found by miners, as long as they don't do things like: duplicate the same work to multiple miners ...
August 13, 2017, 06:53:07 AM
WARNING:
There will be one or more ckpool restarts at 11:00 UTC - in about 1hr 15min
This will cause a failover and failback of all miners.
The failovers and failbacks will be very quick - less than a minute - so there shouldn't be much down time.
... going with the old days where ckpool use to crash and burn regularly, and we also got a lot of blocks at the same time ...
Lets see if this can get us some blocks
I'll be doing the restarts of ckpool to try and resolve the problem from the other day.
It seems to require a lot of 'pressure' to cause the problem since I can't reproduce it myself in a test environment.
Thus I'll be trying the expected solution first - update every node - and then restart every node after I update the main pool node.
If that doesn't resolve it then I'll switch things back again as needed to get it all working again.
Well, the good news is, updates are all in place. The bad new is There will be one or more ckpool restarts at 11:00 UTC - in about 1hr 15min
This will cause a failover and failback of all miners.
The failovers and failbacks will be very quick - less than a minute - so there shouldn't be much down time.
... going with the old days where ckpool use to crash and burn regularly, and we also got a lot of blocks at the same time ...
Lets see if this can get us some blocks
I'll be doing the restarts of ckpool to try and resolve the problem from the other day.
It seems to require a lot of 'pressure' to cause the problem since I can't reproduce it myself in a test environment.
Thus I'll be trying the expected solution first - update every node - and then restart every node after I update the main pool node.
If that doesn't resolve it then I'll switch things back again as needed to get it all working again.
that means we'll accept segwit transactions 
Anyway all working after a rather major case of serendipity ...
Ignore below if you're not interested in the gory details
The problem turned out to be that the new version of ckpool can't handle the sockets passed from the old version, so it just sits there spinning it's wheels doing nothing.
This time I decided to do a full upgrade of all the nodes, in advance, and have them ready to be restarted into the latest code if needed.
However, I made sure one node that no one mines to, was on the latest code, before the main restart, to see if that had any effect during the main pool restart.
At 11:01:13 UTC I started the new version on the main pool, including my changes and the hack/fix for the deadlock, that took control from the old version and then it sat there doing exactly the same thing as last time - nothing.
I tried restarting the 'test' node again to see if it could connect ... nope.
So at 11:03:12 UTC, 2 minutes after the update, I 'thought' I started the old version again, and everything switched back to it OK.
Since I had updated all the node's code, I then proceeded to restart every node, since it was worth doing that then also.
By 11:03:53 all nodes were running the new code, and had reconnected to the pool properly, except one.
In the process I'd skipped the NYA node and it was sitting there not working properly either ... which I noticed about 30 seconds after I'd done everything, and restarted it also.
Now everything was back to working ok ... and I 'thought' we were back with the old code on the main pool again (but every node updated)
Due to luck, I'd missed swapping in the old executable when I restarted the main pool the 2nd time ... ... ... ... I was rather annoyed about it all ... ... ... ... but it was all working ok
Thus I got the answer to what was going on and how to get around it if it happens happen.
Mine on
August 13, 2017, 06:33:47 AM
Curious:
does the pool's code matter in finding blocks? Is there a better pool code for finding more blocks? or is it the hashing power that matters?
does the pool's code matter in finding blocks? Is there a better pool code for finding more blocks? or is it the hashing power that matters?
August 13, 2017, 04:48:37 AM
WARNING:
There will be one or more ckpool restarts at 11:00 UTC - in about 1hr 15min
This will cause a failover and failback of all miners.
The failovers and failbacks will be very quick - less than a minute - so there shouldn't be much down time.
... going with the old days where ckpool use to crash and burn regularly, and we also got a lot of blocks at the same time ...
Lets see if this can get us some blocks
I'll be doing the restarts of ckpool to try and resolve the problem from the other day.
It seems to require a lot of 'pressure' to cause the problem since I can't reproduce it myself in a test environment.
Thus I'll be trying the expected solution first - update every node - and then restart every node after I update the main pool node.
If that doesn't resolve it then I'll switch things back again as needed to get it all working again.
There will be one or more ckpool restarts at 11:00 UTC - in about 1hr 15min
This will cause a failover and failback of all miners.
The failovers and failbacks will be very quick - less than a minute - so there shouldn't be much down time.
... going with the old days where ckpool use to crash and burn regularly, and we also got a lot of blocks at the same time ...
Lets see if this can get us some blocks
I'll be doing the restarts of ckpool to try and resolve the problem from the other day.
It seems to require a lot of 'pressure' to cause the problem since I can't reproduce it myself in a test environment.
Thus I'll be trying the expected solution first - update every node - and then restart every node after I update the main pool node.
If that doesn't resolve it then I'll switch things back again as needed to get it all working again.
August 13, 2017, 03:54:54 AM
Come on let's crack this block!
Jump to: