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

[NotFuzzyWarm]

^^ Considering how cheap they are, get a new SD card. Biggest thing is that you need an AUC3 dongle -- the A6 uses the older AUC2. They are not interchangable. For one source, check Blokforge.com

[1714256539]

1714256539

[1714256539]

1714256539

[1714256539]

1714256539

[BSGMiner]

...Biggest thing is that you need an AUC3 dongle -- the A6 uses the older AUC2...

Thanks. I made sure to get the AUC3 module and connection cables included with the miner.

[EncoreMining]

...Biggest thing is that you need an AUC3 dongle -- the A6 uses the older AUC2...

Thanks. I made sure to get the AUC3 module and connection cables included with the miner.

Congrats. I love my 741s. Still have 9 running and 1 waiting for a new power cord.

[mercurye]

Isn't the 741 losing $US 1 per day? How do you manage that with hosting?

[yxt]

I have a bunch of A741, located in Europe, if anybody is interested --> PM

[BSGMiner]

Isn't the 741 losing $US 1 per day? How do you manage that with hosting?

Not sure if this was directed to me or EncoreMining, but I'd rather mine at near break-even than get involved with the exchanges. That's just my personal preference, though.

Edit: I don't have anything hosted either.

[kano]

KDB restart in about 45 minutes
Restart will be at about 11:30 UTC when the (current) Rem shift completes.

No mining should be affected.

This is a minor update, but includes a change to better support empty blocks in KDB.
While we never want or hope to find empty blocks, the state of the Bitcoin network recently meant there were actually times when the available transactions after a network block change were very small.
We had one during that where there was only 1 transaction available on the network after a network block change.

The pool asicboost support has completed testing also.
After the KDB restart has completed and all is running OK, I'll work out when I'll do the pool update restarts for asicboost.
I've found yet another bug in the pool code, this time regarding failing to submit asicboost blocks, but I've patched in a workaround and tested it.

Restart complete.
From 11:32 UTC to 11:44 UTC

[NotFuzzyWarm]

KDB restart in about 45 minutes
Restart will be at about 11:30 UTC when the (current) Rem shift completes
....
The pool asicboost support has completed testing also.
After the KDB restart has completed and all is running OK, I'll work out when I'll do the pool update restarts for asicboost.
I've found yet another bug in the pool code, this time regarding failing to submit asicboost blocks, but I've patched in a workaround and tested it.

Restart complete.
From 11:32 UTC to 11:44 UTC

Hmm, wonder if a certain other software dev has picked up on that?
Just another reason to mine here. Face it, in one respect pool software is like any other financial software: money is at stake so it had better be thoroughly vetted via testing before entering production status.  If there is a bug(s) not only are actual monies earned at risk but also as in this case, possible earnings. Having a pool op/programmer who knows that is Priceless.

[comby]

The pool asicboost support has completed testing also.
After the KDB restart has completed and all is running OK, I'll work out when I'll do the pool update restarts for asicboost.
I've found yet another bug in the pool code, this time regarding failing to submit asicboost blocks, but I've patched in a workaround and tested it.

does that mean I can add my dragons to kano?

[clgrissom3]

The pool asicboost support has completed testing also.
After the KDB restart has completed and all is running OK, I'll work out when I'll do the pool update restarts for asicboost.
I've found yet another bug in the pool code, this time regarding failing to submit asicboost blocks, but I've patched in a workaround and tested it.

does that mean I can add my dragons to kano?

Not yet, he just restarted the KDB...now he has to restart the pool for everything to go into effect.  That will be sometime today.

[kano]

The pool asicboost support has completed testing also.
After the KDB restart has completed and all is running OK, I'll work out when I'll do the pool update restarts for asicboost.
I've found yet another bug in the pool code, this time regarding failing to submit asicboost blocks, but I've patched in a workaround and tested it.

does that mean I can add my dragons to kano?

Not yet, he just restarted the KDB...now he has to restart the pool for everything to go into effect.  That will be sometime today.

OK planned update for the pool code is 02:00 UTC in about 10.7 hours.
I'll post again not long before that to confirm it.

The update will firstly be the main node behind the scenes, then as long as that goes all OK,
I'll update one of the non-mining nodes and then each of the mining nodes after that.

The first step, updating the main node, may not cause everyone to failover (though of course some miners will)
I think it should be about 10% failing over for that as long as all goes as planned.
Also, I have tested various combinations of versions and having the main one updated worked ok with a node not updated.

The next step of doing each node will failover each miner on the node that I update.
All nodes will be done within about half an hour after I start.

Mine on!

[wavelengthsf]

Woohoo - almost time to point the dragon to the main pool and cross that 200TH threshold!

[noquedaeltiempo]

That's pretty cool, hope we see miners migrating from others pools now that Kano worked out the Asicboost thing!

By the way, anyone selling bitmain coupons? Interested in buying 5 or 6 of >$300 value. Please PM if you have some still.

[minergain.com]

That's pretty cool, hope we see miners migrating from others pools now that Kano worked out the Asicboost thing!

By the way, anyone selling bitmain coupons? Interested in buying 5 or 6 of >$300 value. Please PM if you have some still.

I have a free $100 one that expires at the end of the month.  PM me with your bm info and I'll transfer it.

[kano]

Pool restart and rolling node restart in almost 3 hours at 02:00 UTC
See below for more details

Outages should be at most 2 failovers - i.e. 5 minutes each for 1) main server 2) the node you mine to
But hopefully only 1 failover when the node you mine to is updated - since the main server restart shouldn't failover most miners.

OK planned update for the pool code is 02:00 UTC in about 10.7 hours.
I'll post again not long before that to confirm it.

The update will firstly be the main node behind the scenes, then as long as that goes all OK,
I'll update one of the non-mining nodes and then each of the mining nodes after that.

The first step, updating the main node, may not cause everyone to failover (though of course some miners will)
I think it should be about 10% failing over for that as long as all goes as planned.
Also, I have tested various combinations of versions and having the main one updated worked ok with a node not updated.

The next step of doing each node will failover each miner on the node that I update.
All nodes will be done within about half an hour after I start.

Mine on!

[dzimmerm56]

Umblockchucka Umblockchucka
time for a block everyone!
I sacrificed some egg whites to a very good omelet today, so I have done my part.
Umblockchucka Umblockchucka .......

[BSGMiner]

Pool restart and rolling node restart in almost 3 hours at 02:00 UTC

Failed over and back just fine on NYA & US.

Thanks, Kano

Mining on!

[kano]

Pool restart and rolling node restart in almost 3 hours at 02:00 UTC
See below for more details

Outages should be at most 2 failovers - i.e. 5 minutes each for 1) main server 2) the node you mine to
But hopefully only 1 failover when the node you mine to is updated - since the main server restart shouldn't failover most miners.

OK planned update for the pool code is 02:00 UTC in about 10.7 hours.
I'll post again not long before that to confirm it.

The update will firstly be the main node behind the scenes, then as long as that goes all OK,
I'll update one of the non-mining nodes and then each of the mining nodes after that.

The first step, updating the main node, may not cause everyone to failover (though of course some miners will)
I think it should be about 10% failing over for that as long as all goes as planned.
Also, I have tested various combinations of versions and having the main one updated worked ok with a node not updated.

The next step of doing each node will failover each miner on the node that I update.
All nodes will be done within about half an hour after I start.

Mine on!

All OK and complete since 02:30

There was one hiccough at the start where I had to do a quick change to the main pool code due to it spamming a few messages - so there were 2 early on failovers - the first one just after 02:00 and the second one at 02:10

Unfortunately the failover on the main pool during the first part didn't keep any connections properly, so everyone would have had both of the initial failovers at the start before their individual node failover

All the nodes were switched to the new code by 02:30 as I had hoped to do.

I've pointed one of my T1s at the pool for a while already and it's working fine also.

Mine on!

Anyone having any problems connecting to the pool now since 02:00, but had no problem before 02:00 let me know, so I can know if there were any other problems caused by the changes.

[rifleman74]

MINE ON WITH KANO-SAN!

[ccgllc]

FYI - post about Overt ASICBoost on Kano:

https://bitcointalk.org/index.php?topic=4748860.msg42884970#msg42884970

... and post removed by (anonymous) in under and hour.  Text was:

===

KanoPool (https://www.kano.is) added Overt ASICBoost to its pool a few hours ago.

Kano spent quite some time testing this code and removing bugs, some rumored to have prevented earned block payments, from the code multiple pools use to support Overt ASICBoost.

There should be no worries of 400PH miner being paid for months without earning blocks on Kano, unlike speculation elsewhere.  Non ASICBoost miners won't be saddled with supporting those folks either, since on Kano they will pull their own weight.

Come join the best supported pool on earth:  kano.is.  Public port 3333 nodes in New York, London, Germany, Japan, and Singapore, with the default stratum server in Western USA.

You can chat with us on IRC (#kano.is), Discord (KanoPool), or of course, here at Bitcoin talk (where we have the most active thread on all of Bitcoin Talk, much less the pool subforum).

===

Now posted at https://cryptocurrencytalk.com/topic/107802-kanois-adds-overt-asicboost-to-its-pool/

update:  Deleted off the Halong thread as well as "off topic".