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

For people that love numbers.  Here are my stats for the month with an average of about 15.99 THs.


https://docs.google.com/spreadsheets/d/1TUQ7eEWaMKaAW1QjAHy34KL9nQ09R6dPrRELAH7gG0I/edit?usp=sharing

Hi sorry... I resolved the issue, although it took me 7 hours of trial and error due to the nature of the failure on one of the switches.  Therefore I locked that other thread.

Fortunately, it was NOT PFSense, but rather a Netgear GS316 gone flaky.  Would have been a lot shorter day if it, and an old TP-Link switch I used for testing, had just outright died instead of kinda-work-sometimes.

I've added a new node: UK uk.kano.is
This is the replacement for the NL node that will be switched off at some point.

Firstly, no one needs to do anything, all changes are automatic and DNS is now set so that NL points to UK.

The ping time from the UK node to the main server is a few ms faster than the NL node.
The ping time from the UK node to Iceland is a couple of ms slower than the NL node.
So ... possibly about a ms faster overall

Anyone who reconnects to NL from now on (a few miners have already) will connect to the new UK node.

In 8 hours (12:00 UTC) I'll failover all miners left on the NL node so that they'll automatically reconnect to the UK node.

Mine on!

Gotta add more hash to keep up!   Simple as that.


MINE ON WITH KANO-SAN!!!

Guys I'm looking at the pools stats and this is crazy. We have 40% more hashing power than 6-7 months ago, and yet we are expected to only find 1/2 as many blocks. That's crazy!

Guys I'm looking at the pools stats and this is crazy. We have 40% more hashing power than 6-7 months ago, and yet we are expected to only find 1/2 as many blocks. That's crazy!

...

Yeah you can't use a normal ping on the AWSLS servers - which most on the nodes now are.
You'd need to do a "tcp ping" on port 8080

I've been googling around looking for some easy to use and readily available tcp ping programs - I'll update the first post once I work out the easiest one's to use that are most readily part of the OSes or easiest (and safest) to get.

But for google help - search for "tcp ping" and if you find one, use port 8080 on each node.

ok, now monday 2 or 3 blocks and April is saved...

Argh! Co-locating stinks! Main miner isn't hashing...

Yeah it actually reconnected a few times
All the reconnects were immediate though, so no alerts.
Well the AWS option is in the UK, so I guess that's what I could move it to since it will probably have similar response times for Iceland.
OK that'll be the next node I'll update.

Hi sorry... I resolved the issue, although it took me 7 hours of trial and error due to the nature of the failure on one of the switches.  Therefore I locked that other thread.

I've been mining to Exodus desktop wallet for a while. Today when I opened it I got a warning that it seems like I'm mining there or keep getting small frequent payments and because of the fees adding up from number of small payments they are at the moment over half my balance if I was to send my BTC somwhere else

I paniced for a while, but there must have been something wrong with the info because now when looking at my available balance it's about 96 % of my total balance. Hope this is the case.

Anyway Exodus doesn't seem to be the right choice to mine to. I know I read about Electrum somewhere (maybe that was discussed in this thread) and I also installed it and changed my payout address from Kano there today to try it out. I'll see what happens when the next block matures.

When sending BTC from Electrum there seems to be a setting for the fees depending on how long (how many blocks) I'm prepared to wait for until the transaction. As I find Exodus much more newbie-friendly I was thinking about mining to Electrum for a while (maybe 5 blocks to try it out) and then try to send everything to Exodus at once with the fee setting targeted at, for example within, 10 blocks which would keep the fees down.

Is this a good or bad idea and what would you insted suggest to keep the fees as low as possible?

...
Hi sorry... I resolved the issue, although it took me 7 hours of trial and error due to the nature of the failure on one of the switches.  Therefore I locked that other thread.
...

Ironically it appears that I cannot post on that thread.  I have used pfsense for years and although it mostly works flawlessly, I have seen it with hickups - especially after an update.  If you back it up (I usually do one with everything including RDS and extensions, and one without the addons) then rebuild it.  Once you get to the wizard, just click on the diagnostics menu and restore the backup.  I have found the best luck without the addons and then just manually reinstall those later on.  Not sure if that will help, but may be worth a try since it only takes about 10 minutes.

Hi all.  I had over a PH of Kano hash go offline this morning.  Not a problem with the pool, just had ~150 antminers decide to not talk on my network.  Going nuts trying to figure out whats going on.  Any assistance would be appreciated.  Details at https://bitcointalksearch.org/topic/m.35897218

Thanks a lot for the response!
Is there a quick way to check if the API access is enabled by default? There's an application provided by Ebit that is capable of setting  miners configuration. I don't know how it works exactly (I never even installed it), but I guess it may be using this very same API...

Otherwise... The web interface of Ebit allows very little things to be configured. The cgminer configuration part only allows to set three pools (a combination of a servername, a username and a password). That's it.

And there's no telnet / ssh access, too. There's a guy here on this forum stating he can help to get root access to Ebit devices. But he wants to know the MAC address of the machine, and expects me to install his software (with a pre-defined root password) onto the miner. I don't really want to do it this way. He also mentioned there's a way to get root access by doing some hardware mod (I guess he meant connecting something like a serial console and going through a password recovery routine). But he doesn't want to share the details and I was unable to find any other information about it.

If there's anyone successfully using an API to monitor (or maybe even control?) Ebit devices, please share your experience!

Excellent But stick to port 8080 but don't use 3333

The reason to use tcping, is to compare the different nodes to work out which is closest.
But don't take too much notice of the actual numbers it returns vs a normal ping