Pages:
Author

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

legendary
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
3 blocks in one day! damn! nice! really wish I was back in the pool Sad  looks like the hash rate is steady now and not really fail over any more. as the average hash rate is now close to 300 ph/s

Looks 400ish PH/s to me:

legendary
Activity: 2254
Merit: 2419
EIN: 82-3893490
3 blocks in one day! damn! nice! really wish I was back in the pool Sad  looks like the hash rate is steady now and not really fail over any more. as the average hash rate is now close to 300 ph/s
hero member
Activity: 1610
Merit: 538
I'm in BTC XTC
A triple kanopool Block Partytm!! Can't beat that with a stick!   Cheesy
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
Block by Canaan!!  Cheesy

This is our 3rd of BLOCK SUNDAY! Cheesy Cheesy Cheesy
In my country (GMT+7), it's Monday now. Anyway, 3 blocks is really a fantastic number. Cheer!

The pool does everything by the UTC clock Cheesy
legendary
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
Who needs two when you can have three Tongue


newbie
Activity: 25
Merit: 0
Block by Canaan!!  Cheesy

This is our 3rd of BLOCK SUNDAY! Cheesy Cheesy Cheesy
In my country (GMT+7), it's Monday now. Anyway, 3 blocks is really a fantastic number. Cheer!
legendary
Activity: 1554
Merit: 2037
Nothing like a 3 blocks on a sick day to make you feel better.

Turkey soup it is.  Mine on folks.


legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
Block by Canaan!!  Cheesy

This is our 3rd of BLOCK SUNDAY! Cheesy Cheesy Cheesy
hero member
Activity: 1063
Merit: 502
RIP: S5, A faithful device long time
Hey mining buddys,

Hope i get back on pool soon. Undecided
legendary
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
Who needs one when you can have two  Smiley


full member
Activity: 658
Merit: 118
Alright! Been a while since a proper block sunday!
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
Another luckyant block! Cheesy

This is our 2nd of BLOCK Sunday! Cheesy Cheesy
legendary
Activity: 1736
Merit: 1032
Carl, aka Sonny :)
As mentioned before - certainly no problem with failing over ... or ...
Block! by luckyant Cheesy

Yay luckyant failover block!  This is our 1st of BLOCK SUNDAY! Cheesy
legendary
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
As mentioned before - certainly no problem with failing over ... or ...
Block! by luckyant Cheesy

Finally! First block of 2019  Cheesy
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
As mentioned before - certainly no problem with failing over ... or ...
Block! by luckyant Cheesy
legendary
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
Like any miner, you should always have backup pool settings, and thus when the main pool has problems, updates, changes, whatever, you failover to one of your backup pool settings.
In this case of course it's to us here Smiley

As discussed in discord, there's certainly no problem with them doing it, and their luck proves it's all ok for them to do it, and you can't hop pools to your advantage, so it's all good.

strange tactics to have so long PPL5NS pool for failover, for 1-2h failover imho better use some pps pool.

They should stay in this pool and use it as primary, secondary and tertiary (plenty of mirrors) imo.
I'm using these:

stratum+tcp://nya.kano.is:3333
stratum+tcp://stratum.kano.is:3333
stratum+tcp://stratum80.kano.space:80

The bigger their operation, the more useful it is to remain in the PPLNS pool, as blocks (and payments) would come so often the variance would be averaged quickly and they would end earning more in the long run...
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Like any miner, you should always have backup pool settings, and thus when the main pool has problems, updates, changes, whatever, you failover to one of your backup pool settings.
In this case of course it's to us here Smiley

As discussed in discord, there's certainly no problem with them doing it, and their luck proves it's all ok for them to do it, and you can't hop pools to your advantage, so it's all good.

strange tactics to have so long PPL5NS pool for failover, for 1-2h failover imho better use some pps pool.
PPS is always higher, usually much higher, fees - anyone with a large hash rate should see that as a bad idea ... and it's been quite a number of hours ... up and down.
member
Activity: 159
Merit: 12
Like any miner, you should always have backup pool settings, and thus when the main pool has problems, updates, changes, whatever, you failover to one of your backup pool settings.
In this case of course it's to us here Smiley

As discussed in discord, there's certainly no problem with them doing it, and their luck proves it's all ok for them to do it, and you can't hop pools to your advantage, so it's all good.

strange tactics to have so long PPL5NS pool for failover, for 1-2h failover imho better use some pps pool.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Well the base hash rate is still around 45-50PH, and the rest is failover.


I don't try and mislead the miners about the pool hash rate, unlike ckpool who has not changed their hash rate down for about 10 days that it's been well under half what it says.

Well that one is currently doing 8PH at the moment for what is worth. But then this means there is 450PH worth of hash rate using your pool only when another one fails? Is there any advantage to them doing that?

Like any miner, you should always have backup pool settings, and thus when the main pool has problems, updates, changes, whatever, you failover to one of your backup pool settings.
In this case of course it's to us here Smiley

As discussed in discord, there's certainly no problem with them doing it, and their luck proves it's all ok for them to do it, and you can't hop pools to your advantage, so it's all good.
legendary
Activity: 2030
Merit: 1569
CLEAN non GPL infringing code made in Rust lang
Well the base hash rate is still around 45-50PH, and the rest is failover.


I don't try and mislead the miners about the pool hash rate, unlike ckpool who has not changed their hash rate down for about 10 days that it's been well under half what it says.

Well that one is currently doing 8PH at the moment for what is worth. But then this means there is 350PH worth of hash rate using your pool only when another one fails? Is there any advantage to them doing that?
Pages:
Jump to: