HOW IN THE UNIVERSE DID YOU CREATE A BITCOIN ADDRESS WITH KANO AFTER THE ONE?
?I want one with panagiporets after the 1
Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 232. (Read 5352229 times)
May 07, 2018, 11:05:43 PM
HOW IN THE UNIVERSE DID YOU CREATE A BITCOIN ADDRESS WITH KANO AFTER THE ONE?
?I want one with panagiporets after the 1
May 07, 2018, 11:04:37 PM
so, lets prove me wrong, re-start the pool and lets see what happens! :-)
May 07, 2018, 11:01:48 PM
*snip*
I was waiting fort that response. I'm pretty sure I remember that same post by you in the last few months, probably close to verbatim.
Mine on
May 07, 2018, 11:01:13 PM
...
Persoanlly, I think there is an issue in some detail yet to be discovered, that after the pool runs for an extended period of time, or so many shares, blocks are not found as near 100% as they should. ( when you use "probability" alone )
Persoanlly, I think there is an issue in some detail yet to be discovered, that after the pool runs for an extended period of time, or so many shares, blocks are not found as near 100% as they should. ( when you use "probability" alone )
Interesting theory...what changes during a mass reboot? vardiff readjusting for all workers is the one thing I think of, what else?
Shares (and blocks) are found by miners, not by the pool.
All shares that arrive are first checked/hashed by ckpool, then checked/hashed, from scratch, more accurately by KDB.
That's the only thing that shows if we find a block.
Any share that arrives, and hashes to a value that would produce a block, is displayed by KDB on the web site, no matter what other issues may occur.
(late, orphan, etc etc)
Any suggestion about random events causing blocks is actually caused by faulty memory
It's called 'Confirmation Bias' https://en.wikipedia.org/wiki/Confirmation_bias or in the more severe cases Cognitive Bias https://en.wikipedia.org/wiki/Cognitive_bias
It's typical to remember outstanding events and not notice the rest.
HOW IN THE UNIVERSE DID YOU CREATE A BITCOIN ADDRESS WITH KANO AFTER THE ONE?
?I want one with panagiporets after the 1
May 07, 2018, 10:46:23 PM
...
Persoanlly, I think there is an issue in some detail yet to be discovered, that after the pool runs for an extended period of time, or so many shares, blocks are not found as near 100% as they should. ( when you use "probability" alone )
Persoanlly, I think there is an issue in some detail yet to be discovered, that after the pool runs for an extended period of time, or so many shares, blocks are not found as near 100% as they should. ( when you use "probability" alone )
Interesting theory...what changes during a mass reboot? vardiff readjusting for all workers is the one thing I think of, what else?
Shares (and blocks) are found by miners, not by the pool.
All shares that arrive are first checked/hashed by ckpool, then checked/hashed, from scratch, more accurately by KDB.
That's the only thing that shows if we find a block.
Any share that arrives, and hashes to a value that would produce a block, is displayed by KDB on the web site, no matter what other issues may occur.
(late, orphan, etc etc)
Any suggestion about random events causing blocks is actually caused by faulty memory
It's called 'Confirmation Bias' https://en.wikipedia.org/wiki/Confirmation_bias or in the more severe cases Cognitive Bias https://en.wikipedia.org/wiki/Cognitive_bias
It's typical to remember outstanding events and not notice the rest.
May 07, 2018, 10:44:06 PM
Not much, but added another S9 today. Going to be interesting when summer really hits here in Texas!
Current temps are high of 76 on one, and 84 another. Need some more 6 inch duct to bring the 84 down to in the 70's!
Now lets gets some freakin BTCLOCKS BTCABY!!!
Current temps are high of 76 on one, and 84 another. Need some more 6 inch duct to bring the 84 down to in the 70's!
Now lets gets some freakin BTCLOCKS BTCABY!!!
Mine run up to 105C , it'll be fine
May 07, 2018, 09:56:55 PM
Goodmorning from Greece, noob alert here, can you tell me if I need to make backups of the wallet.dat file from bitcoin core more than once, I have stored it in multiple usbs, do I need to take backups regurarly after some transactions or just once is enough?
Back it up every time after you create a new receiver address. It those private keys you want to hold onto. That said, I think most wallets create those in batches, like 100 at a time.
May 07, 2018, 09:56:05 PM
I vote for a pool re-start.
And what pray tell would you expect that to accomplish? Besides causing all of us to fail over to our backup pools that is?P.S. New sig: Kano Pool Blocks... No restart required.
If you look back in history. Everytime there has been long blocks, and then a "restart" for one reason or another there has been a block found very shortly after, and the near 100 % will continue for a while.
I have seen this numerous times since December that this happens almost like clock work.
YES, saying that it does nothing, becuase of probability, can be an accurate statement, but when this happens too often, there is more to this than just probability.
I dont remember the date, but a while ago, Kano said he needed to do a pool restart due to a logging issue, and then the double restart cuased another issue, and he found why in the code this issue happened. after that, blocks were normal again, near 100 % but prior to that there were long blocks.. like now.
Persoanlly, I think there is an issue in some detail yet to be discovered, that after the pool runs for an extended period of time, or so many shares, blocks are not found as near 100% as they should. ( when you use "probability" alone )
Interesting theory...what changes during a mass reboot? vardiff readjusting for all workers is the one thing I think of, what else?
May 07, 2018, 09:53:04 PM
Goodmorning from Greece, noob alert here, can you tell me if I need to make backups of the wallet.dat file from bitcoin core more than once, I have stored it in multiple usbs, do I need to take backups regurarly after some transactions or just once is enough?
May 07, 2018, 09:35:22 PM
I vote for a pool re-start.
And what pray tell would you expect that to accomplish? Besides causing all of us to fail over to our backup pools that is?P.S. New sig: Kano Pool Blocks... No restart required.
If you look back in history. Everytime there has been long blocks, and then a "restart" for one reason or another there has been a block found very shortly after, and the near 100 % will continue for a while.
I have seen this numerous times since December that this happens almost like clock work.
YES, saying that it does nothing, becuase of probability, can be an accurate statement, but when this happens too often, there is more to this than just probability.
I dont remember the date, but a while ago, Kano said he needed to do a pool restart due to a logging issue, and then the double restart cuased another issue, and he found why in the code this issue happened. after that, blocks were normal again, near 100 % but prior to that there were long blocks.. like now.
Persoanlly, I think there is an issue in some detail yet to be discovered, that after the pool runs for an extended period of time, or so many shares, blocks are not found as near 100% as they should. ( when you use "probability" alone )
May 07, 2018, 09:34:34 PM
I vote for a pool re-start.
And what pray tell would you expect that to accomplish? Besides causing all of us to fail over to our backup pools that is?P.S. New sig: Kano Pool Blocks... No restart required.
It did work rather well back in September/October. Within an hour of restart, block was found.
MINE ON WITH KANO-SAN!
May 07, 2018, 09:31:22 PM
I vote for a pool re-start.
And what pray tell would you expect that to accomplish? Besides causing all of us to fail over to our backup pools that is?P.S. New sig: Kano Pool Blocks... No restart required.
May 07, 2018, 09:20:21 PM
Last Share (w_lastshare) for a worker.
If it's more than 120 seconds old then the miner isn't sending shares to the pool any more.
Yes, I read the description you posted some time ago, and I fully agree - it's a great way to see if a miner went offline for any reason. But it won't let me see if a miner lost some power (i.e. due to a failed hash board). If it's more than 120 seconds old then the miner isn't sending shares to the pool any more.
That's why I would like to check for the hashrate, as (under the normal conditions) the hashrate is expected to be at about the same level - at least it shouldn't drop significantly. Hence, my question of whether I understand the meaning of w_hashrate5m / w_hashrate1h / w_hashrate24hr properly (I guess I don't).
If you have a lot of miners, and don't have any reliable direct miner monitoring software, it's best to look at the workers page once in a while
and then click on the 2 different sortings at the top
"Last Share" and "Hash Rate"
and see what's at the bottom.
You can also use the "Shift Graph" to see how a single worker is performing over time.
I have successfully used the shift graph to diagnose problems w/my farm. I had a psu that melted the breakout board and I noticed a 2/3 hashrate drop on that worker when ambient temps were warm during the day. also had an airflow issue on one worker during warm ambient temps causing a hashboard shutdown. checking the worker page gave me cause for concern...but not panic, but the shift graph gave me solid evidence there was something wrong. In both cases the pool stats were enough for me to diagnose a problem if I could interpret the data right. When my psu went down I saw that worker drop by 2/3 of both hashrate and share rate, then followed up by downward line on the shift graph, bottoming out at 1/3 of normal hash for that machine. A "long share" would not cause this type of data. sure enough (i use hp server psus...2 per machine) the breakout board chernobyled on the "2 hashboard" psu. fresh psu...and all good. Same deal w/my s9 when it sucked a leaf...combo of rising ambient temps, then share rate/hashrate drop and worker graph drop on the shift graph. There's a pattern in the data that you can use to diagnose problems purely from Kano's stats, but you gotta interpret it right!
May 07, 2018, 09:13:02 PM
I vote for a pool re-start.
And what pray tell would you expect that to accomplish? Besides causing all of us to fail over to our backup pools that is?
May 07, 2018, 09:01:22 PM
I vote for a pool re-start.
May 07, 2018, 07:33:54 PM
I am legendary, can you do something bigger
May 07, 2018, 07:19:21 PM
Big Welcome to our new members!!! If anyone would like to help Spread the word and, spark the interest of potential new members,
here's a few Kano Pool Signature Banners:
How to add it:
Go to profile>forum profile information>paste in signature box>change profile button>enjoy!
note: be sure to copy everything correctly. Results vary depending on forum rank.
Ex:
Try Kano Pool
Ex:
I Mine at Kano Pool
Ex:
The Best BTCitcoin Pool in the World: Kano Pool
here's a few Kano Pool Signature Banners:
How to add it:
Go to profile>forum profile information>paste in signature box>change profile button>enjoy!
note: be sure to copy everything correctly. Results vary depending on forum rank.
Ex:
Try Kano Pool
Code:
[b][url=https://kano.is/]Try Kano Pool [/url] [/b]
Ex:
I Mine at Kano Pool
Code:
[b]I Mine at [url=https://kano.is/]Kano Pool [/url] [/b]
Ex:
The Best BTCitcoin Pool in the World: Kano Pool
Code:
[b]The Best [btc]itcoin Pool in the World: [url=https://kano.is/]Kano Pool [/url] [/b]
Thanks BTCro, I changed mine but only can do the basic one I guess!
May 07, 2018, 07:18:00 PM
Not much, but added another S9 today. Going to be interesting when summer really hits here in Texas!
Current temps are high of 76 on one, and 84 another. Need some more 6 inch duct to bring the 84 down to in the 70's!
Now lets gets some freakin BTCLOCKS BTCABY!!!
Current temps are high of 76 on one, and 84 another. Need some more 6 inch duct to bring the 84 down to in the 70's!
Now lets gets some freakin BTCLOCKS BTCABY!!!
May 07, 2018, 06:42:28 PM
Big Welcome to our new members!!! If anyone would like to help Spread the word and, spark the interest of potential new members,
here's a few Kano Pool Signature Banners:
How to add it:
Go to profile>forum profile information>paste in signature box>change profile button>enjoy!
note: be sure to copy everything correctly. Results vary depending on forum rank.
Ex:
Try Kano Pool
Ex:
I Mine at Kano Pool
Ex:
The Best BTCitcoin Pool in the World: Kano Pool
here's a few Kano Pool Signature Banners:
How to add it:
Go to profile>forum profile information>paste in signature box>change profile button>enjoy!
note: be sure to copy everything correctly. Results vary depending on forum rank.
Ex:
Try Kano Pool
Code:
[b][url=https://kano.is/]Try Kano Pool [/url] [/b]
Ex:
I Mine at Kano Pool
Code:
[b]I Mine at [url=https://kano.is/]Kano Pool [/url] [/b]
Ex:
The Best BTCitcoin Pool in the World: Kano Pool
Code:
[b]The Best [btc]itcoin Pool in the World: [url=https://kano.is/]Kano Pool [/url] [/b]
May 07, 2018, 06:24:41 PM
Last Share (w_lastshare) for a worker.
If it's more than 120 seconds old then the miner isn't sending shares to the pool any more.
Yes, I read the description you posted some time ago, and I fully agree - it's a great way to see if a miner went offline for any reason. But it won't let me see if a miner lost some power (i.e. due to a failed hash board). If it's more than 120 seconds old then the miner isn't sending shares to the pool any more.
That's why I would like to check for the hashrate, as (under the normal conditions) the hashrate is expected to be at about the same level - at least it shouldn't drop significantly. Hence, my question of whether I understand the meaning of w_hashrate5m / w_hashrate1h / w_hashrate24hr properly (I guess I don't).
If you have a lot of miners, and don't have any reliable direct miner monitoring software, it's best to look at the workers page once in a while
and then click on the 2 different sortings at the top
"Last Share" and "Hash Rate"
and see what's at the bottom.
You can also use the "Shift Graph" to see how a single worker is performing over time.
Jump to: