Author

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

legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
My first is: stratum+tcp://stratum.kano.is:3333

If that connection goes down I have this: stratum+tcp://stratum80.kano.is:80

Is it possible for stratum 3333 to go down and stratum80 to still work?  

It could be if 3333 is down that 80 will be down as well and what I'm doing is negligible. 

I would think so under a certain circumstance.  Is it worth it to do that and have another pool for third?
Both ports point to the same ckpool instance.
If one port got blocked due to a ddos or other such issues not part of ckpool, then having the 2nd one would help in that case.
ckdb only supports one backend ckpool at the moment and that's not high on the priorities so will be a way off before that's changed.
cgminer itself handles having multiple active and multiple backup pools - as you realise - and that should resolve any pool outages.

P.S. I've switched ckpool over to the latest version already also.
sr. member
Activity: 478
Merit: 250
i did notice that. i also noticed my best share actually shows up for the solo pool. it was my first time there since switching my failover pool earlier today.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
For anyone who noticed?
The pool just took a nose dive and crashed.
I've been running an older version of ckpool while ckolivas has been fixing a few problems on the solo pool.
One of the old problems (that has been fixed) reared it's head and took out the pool.
I'm still running that version (when I restarted it after the crash) but will probably move to the latest version now solo seems to be stable.
That should simply be a reconnect message in cgminer when I switch and no real outage or failover when I do it shortly.
Sorry for the short outage that happened.
legendary
Activity: 1019
Merit: 1001
Spectreproject Community Manager
... and a bit of news, especially for those who have been mining here since we started in September.

That last block we just got, 339388, https://blockchain.info/block/00000000000000000088ea4d769abcf758d8d18d68d457abf083e515c4d12437
it the 100th successful block we've found (plus one orphan after the 1st block we found)

Happy 100 everyone Cheesy

and Happy 100th to you along with congratulations to you and CK on a great pool.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Payout 339298 sent and confirmed
... and we got block 101 while I was doing that Smiley
Payout 339316 sent and confirmed
sr. member
Activity: 471
Merit: 250
Damn we are on fire today!

Yep, all going well  Cheesy

My hash power will be down for 16hrs due to a local electricity supplier problem  Angry

hero member
Activity: 1249
Merit: 506
Damn we are on fire today!
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
... and a bit of news, especially for those who have been mining here since we started in September.

That last block we just got, 339388, https://blockchain.info/block/00000000000000000088ea4d769abcf758d8d18d68d457abf083e515c4d12437
it the 100th successful block we've found (plus one orphan after the 1st block we found)

Happy 100 everyone Cheesy

Would you be able to list the block numbers on the website with reverse numbering, but same order, so that we can see the "true" block #?  Right now #1 is actually #100.

M
IRC half an hour ago Smiley
Code:
07:57 < kanoi_> (the actual block # on the blocks page is somewhere far down the todo list :P)
hero member
Activity: 1249
Merit: 506
... and a bit of news, especially for those who have been mining here since we started in September.

That last block we just got, 339388, https://blockchain.info/block/00000000000000000088ea4d769abcf758d8d18d68d457abf083e515c4d12437
it the 100th successful block we've found (plus one orphan after the 1st block we found)

Happy 100 everyone Cheesy
Congrats everyone. I haven't been here since the beginning,  but it's been a fun few months!
legendary
Activity: 1540
Merit: 1001
... and a bit of news, especially for those who have been mining here since we started in September.

That last block we just got, 339388, https://blockchain.info/block/00000000000000000088ea4d769abcf758d8d18d68d457abf083e515c4d12437
it the 100th successful block we've found (plus one orphan after the 1st block we found)

Happy 100 everyone Cheesy

Would you be able to list the block numbers on the website with reverse numbering, but same order, so that we can see the "true" block #?  Right now #1 is actually #100.

M
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
... and a bit of news, especially for those who have been mining here since we started in September.

That last block we just got, 339388, https://blockchain.info/block/00000000000000000088ea4d769abcf758d8d18d68d457abf083e515c4d12437
it the 100th successful block we've found (plus one orphan after the 1st block we found)

Happy 100 everyone Cheesy
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
As I'm relatively new to mining, sorry if this is a silly question that just everyone knows.

Looking at the worker page on kano.is it says my total is 7th/sec, but looking at each miner individually they show a total of 11.4th/sec, where does that discrepancy come from?

I think one is an instant hash rate and one is an average.  I would imagine after a few shifts they'll be closer to matching.

5min average/ 1Hr average Kano said it was dynamic few pages back.
Yep the 5min value is there coz people have wanted to see it change when they start mining - but it jumps around a lot of course.
The 1hr value should be the value of interest.
However, if you haven't been mining for an hour yet, it doesn't show the "1hr" value Smiley
sr. member
Activity: 440
Merit: 250
As I'm relatively new to mining, sorry if this is a silly question that just everyone knows.

Looking at the worker page on kano.is it says my total is 7th/sec, but looking at each miner individually they show a total of 11.4th/sec, where does that discrepancy come from?

I think one is an instant hash rate and one is an average.  I would imagine after a few shifts they'll be closer to matching.

5min average/ 1Hr average Kano said it was dynamic few pages back.
member
Activity: 65
Merit: 10
As I'm relatively new to mining, sorry if this is a silly question that just everyone knows.

Looking at the worker page on kano.is it says my total is 7th/sec, but looking at each miner individually they show a total of 11.4th/sec, where does that discrepancy come from?

I think one is an instant hash rate and one is an average.  I would imagine after a few shifts they'll be closer to matching.
hero member
Activity: 777
Merit: 1003
And another! Smiley Turning into a good day.

This was nice to wake up to ... Smiley

looks like you put a lot of work in Kano, hope you were able to take  a break

It looks like he spent his whole Saturday working on it.  Shocked
I too hope he took some breaks throughout the day.  Smiley
full member
Activity: 224
Merit: 100
And another! Smiley Turning into a good day.

This was nice to wake up to ... Smiley

looks like you put a lot of work in Kano, hope you were able to take  a break

And another one this morning too Smiley
legendary
Activity: 1019
Merit: 1001
Spectreproject Community Manager
And another! Smiley Turning into a good day.

This was nice to wake up to ... Smiley

looks like you put a lot of work in Kano, hope you were able to take  a break
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Payouts 339142, 339178, 339183 just sent
and confirmed

Edit: oh and all 3 used the new 50 minutes shifts so the 5N value was a bit bigger again due to the rounding up to the shift boundary
Payout 339225 sent
Confirmed
full member
Activity: 159
Merit: 100
hero member
Activity: 1249
Merit: 506
And another! Smiley Turning into a good day.
Jump to: