KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2436 blocks

[firetreeactual]

...This is getting really far off-topic. If you want to discuss further it should be elsewhere.  Before kano yells at us.
...

This thread would lose about 1100 pages if it were pruned to "on topic" posts. 

Take a look at deepinthemines.com. I had a recent conversation re the 1KW HP bricks w/breakouts I use, but had a bad batch of pigtails from a previous supplier. They have put together a PSU package that works with that configuration for my A6, A721, and three S7s. It would do well for your instance, and is cost effective. I have only 110V, and so this approach has worked well for a couple of years through S2s, S3s, S7s, A6s, and now an A7. Never bought an S9, but it would do nicely.

[1715374400]

1715374400

[1715374400]

1715374400

[1715374400]

1715374400

[1715374400]

1715374400

[Dak1]

My phone crashed and I had to get a new one. However, I can't remember what the 2nd authentication app was called and it didn't update to my new phone. Any help would be greatly appreciated.

[gt_addict]

Only 2FA app I know of is Google Authenticator. But if its not on your phone then I doubt it will have the information stored when you do download it again.

[darval]

My phone crashed and I had to get a new one. However, I can't remember what the 2nd authentication app was called and it didn't update to my new phone. Any help would be greatly appreciated.

I discovered that problem when I switched to an iPhone 7.  On googling the problem I was pointed at Authy, an alternative authenticator app which has been working well for me - and its/your keys are backed up in case you have to reinstall (with all the caveats that your keys are only as safe as your backups).

[kano]

My phone crashed and I had to get a new one. However, I can't remember what the 2nd authentication app was called and it didn't update to my new phone. Any help would be greatly appreciated.

Android: Google Play 'FreeOTP Authenticator' by Red Hat
Apple: App Store 'OTP Auth' by Roland Moers

[kano]

Sorry, what does "NYA" mean? I missed it. Google doesn't help me. It showed as "New Zealand"

https://bitcointalk.org/index.php?topic=789369.msg17238254#msg17238254

[kano]

Well I'll add regarding HW errors.

As long as the miner isn't failing due to overheating/pushing it too hard/whatever, what you actually want to compare is the accepted hash rate.
The Workers->Shifts statistics and Workers->Shift Graph will show that.
HW errors, stales, etc don't count in what you get rewarded.
Your rewarded hash rate is purely just accepted valid shares.
If that goes down (or up) after a few days then you'll know if it was better or worse due to the update.
Though, finding a block is certainly gonna reward better than not finding one

I always thought that you want your err rate at or below .01%, otherwise your are wasting power for no increase in hash rate. Especially when you are OC'ing the miner. So better to have .0005 err and 4.8 Th then .05 err and 4.95 TH. Is that a true statement?

Well yeah that (bolded part) is basically what I said
Edit: OK I clearly didn't read that properly - NO you don't want a lower Accepted Hash Rate!
You want the higher rate of whatever is shown on the pool.

The only catch is that what Bitmain miners report, and what you are really getting accepted, are not exactly the same.

When I modified the S1/S2/S3 (years ago) I added "Paid GH/s" which is really what matters. "Diff Accepted" / "Elapsed"
(Bitmain of course never added it)
That number is effectively what's shown on the web site.

[VRobb]

Well it's been 1 year since I started mining here on kano-ckpool - actually been 1 year since I got into mining in the first place, I know a bit late but so far very interesting.  In just 1 year I went from a single S5 barely pumping out 1THs, to an S7, and then to two R4 units which will be sending 16.7THs to the pool (once the second one arrives and gets running!)  
Geeze, glad the ND didn't increase by 16 times like my hashrate did!!  

Mine on, kano-ites!  

[Dak1]

Thank you for your help! 

[philipma1957]

Well after checking options with the. 2 and 1/3 s9 old firm ware gear.

Upgrade to auto tune will make them too loud.

We moved them all from the solar loft and put them in buysolars basement for heating.

So we have to run fans at 50 % and set freq at 525.

Thus auto tune won't be viable for about 120 days.

It is pretty clear to me the old firm ware sucks at block finding.

Kane's stats show it.

And the guy that spent 325 btc solo mining  on nice hash with far better luck at .01 or 10 th settings.

(No s9s at that setting). Really indicate the old s9 firm ware sucks.

Soooooooo we will point the 27th at f2pool.

And keep the avalons pointed here.  13th

If your setup forces you to lower fans and not use auto tune I guess f2 pool should suffer. For it not kano

[Megaquake]

Well after checking options with the. 2 and 1/3 s9 old firm ware gear.

Upgrade to auto tune will make them too loud.

We moved them all from the solar loft and put them in buysolars basement for heating.

So we have to run fans at 50 % and set freq at 525.

Thus auto tune won't be viable for about 120 days.

It is pretty clear to me the old firm ware sucks at block finding.

Kane's stats show it.

And the guy that spent 325 btc solo mining  on nice hash with far better luck at .01 or 10 th settings.

(No s9s at that setting). Really indicate the old s9 firm ware sucks.

Soooooooo we will point the 27th at f2pool.

And keep the avalons pointed here.  13th

If your setup forces you to lower fans and not use auto tune I guess f2 pool should suffer. For it not kano

wow that's insane, all the BTC invested in those s9's, glad I did not get any

[ComputerGenie]

...Upgrade to auto tune will make them too loud...

And another one that bought a Lamborghini Countach and wants to turn it into a VW Beetle 

[xxxgeniy]

BTClock! by btccro with 227.19THs! First Block Today!

[zOU]

It looks like one of the S5 I have in a remote DC died.
Lost 1 board 3 days ago (half hash rate) and lost connection to it yesterday...

So 1 S5 and 1 S7 remain pointed to Kano until I can get it restarted by someone or have a look at it...

[-ck]

ALso i have a huge concern that the orphan block you got along with the problem of block submittin ck had .  The timing of the two sure seem suspicious.  What i think happen is you messed with code to support segwit and its not compatible with something your software is doing.  Odd that both happen at same time  look at the dates of ck post and the date of your orphan

The fuck up in my segwit code was purely on my part with the solo code which is different to the publicly released ckpool code. Additionally the solo code fuck up didn't even generate blocks so there's no way they can even become orphans which are otherwise valid blocks.  Kano doesn't have access to the solo ckpool code and the kano.is pool has not changed its ckpool code in many months; it currently does not have any support for segwit, and as most people on this thread are well aware, Kano himself is against segwit so would only adopt newer code if segwit actually activated. Your fears are unfounded.

[kano]

ALso i have a huge concern that the orphan block you got along with the problem of block submittin ck had .  The timing of the two sure seem suspicious.  What i think happen is you messed with code to support segwit and its not compatible with something your software is doing.  Odd that both happen at same time  look at the dates of ck post and the date of your orphan

The fuck up in my segwit code was purely on my part with the solo code which is different to the publicly released ckpool code. Additionally the solo code fuck up didn't even generate blocks so there's no way they can even become orphans which are otherwise valid blocks.  Kano doesn't have access to the solo ckpool code and the kano.is pool has not changed its ckpool code in many months; it currently does not have any support for segwit, and as most people on this thread are well aware, Kano himself is against segwit so would only adopt newer code if segwit actually activated. Your fears are unfounded.

Well yeah but also - he was implying there was something wrong with the block itself.
That's clearly false - blockchain.info accepted the block and even saw it before the other.
He's just making up crap that doesn't even match facts - I think I'll just delete his post - it's bullshit anyway.

[AmbH]

Just a quick thank you, Kano, for NYA node. Switched over 2 days ago and am seeing better ping times and reduced error rates. Encourage those on or near US east coast to test the node. Thanks again!

[blockchainmines]

Well it's something I added to CKDB long ago to be able to change the miner reward (to put it up twice before)
Here's the message just now:

Code:

[2016-12-16 22:13:02.186+11] process_pplns(): *** block 443699 payout reward overridden, was 1278060860 now 1389667900 = 111607040 (8.7325%) more

There was also something I was waiting on this block for that really had me wondering if it was some sort of vengeance by the block Gods
I created another node to test a less modified version of 0.13.1 so I can use it on all the nodes except the main pool - to send/receive blocks to/from the fibre block relay network faster. That pretty much requires 0.13.1 to optimise it's use.
And yep, yay, that block was properly submitted and accepted on the test node so that's all good now too, I'll update all the nodes - except the main pool - in the next day to 0.13.1 without segwit

This may be a silly question and I may have missed a thread that could have explained this but here you go.  Why wouldn't you do the same update to the main pool?  

The main pool generates the work, all (main and nodes) submit blocks.
Submitting a block on a node that no one is mining to, has no chance of causing any problems if it fails.
The initial test worked fine.

I've now switched 3 of the nodes over to the 0.13.1 version.
Aside: the SG node is now a new one, no longer linode. I've also setup a us-east node so it's close to the us-east fibre relay.
The 0.13.1 has, of course, continued to work as expected on the 3 nodes with the new blocks

The work generation for core bitcoind is different now because they have put segwit in it and I'll need to do work generation testing (without segwit) before I switch that over.
Simply, it will require more testing than needed for nodes.

Everything is either 0.13.0 or 0.13.1, but 0.13.1 has a small advantage with using the fibre relay.

So what is Las Vegas Running as opposed to New York.  I live closer to Las Vegas so that would seem like the obvious choice and my latency is 48ms  while my latency is 63ms to NewYork.  If New York is running more up to date code 13.1, would it make sense to point my miners that direction despite the slight increase in latency?

[ZACHM]

Everything is running the same code. It is just another node to connect to. For those further from the main server in Nevada it helps reduce stales.

[cryptichermit]

Well after checking options with the. 2 and 1/3 s9 old firm ware gear.

Upgrade to auto tune will make them too loud.

We moved them all from the solar loft and put them in buysolars basement for heating.

So we have to run fans at 50 % and set freq at 525.

Thus auto tune won't be viable for about 120 days.

It is pretty clear to me the old firm ware sucks at block finding.

Kane's stats show it.

And the guy that spent 325 btc solo mining  on nice hash with far better luck at .01 or 10 th settings.

(No s9s at that setting). Really indicate the old s9 firm ware sucks.

Soooooooo we will point the 27th at f2pool.

And keep the avalons pointed here.  13th

If your setup forces you to lower fans and not use auto tune I guess f2 pool should suffer. For it not kano

Why not just hack the cgi and unlock your fan setting?