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

Block! by BlockBadger
S9v2 (prolly a T9)
2.4BTC txn fees

I might just block "auth.minerlink.com" at DNS and my router in preparation for when it starts to resolve?

Or perhaps it's just something they utilise at hashnest to manage their miners.

6 chips less per board will always create less heat.

Well I have certain bias to Canaan Avalon as is obvious, also coz they are more reliable according to the few people I have spoken to with a lot of each.
I've no idea how the price/power costs are any more since they've all changed over the past month or so, so you'd have to check and compare, but also take into consideration dealing with returns, and lost hashing time, and each companies record on handling that.

Kano recommend to buy now? So I have many problems with the S9 antminer. I read that the T9 were more efficient than the s9 in relation to temperature.

Comparative temperature S9 vs T9

https://www.youtube.com/watch?v=yHJzo7A312c

Block! by temptrol
A7v1
1.76BTC txn fees

I got booted out of the cgminer team - so don't ask me
Ask the cgminer guy who bitmain pays for pretty much all the code he writes

Would it make sense to try to fork the code and update the miner with a new version that eliminates the send_mac and setup_send_mac_socket functions entirely?

... no you don't get paid for stale shares ...
Just like we don't get paid for a stale block coz it's worthless.

Meanwhile, I spent some time going though the bmminer code to see if they were still faking their stale stats by "hiding" the stale shares.
The reason being to compare your stales since if one miner is reporting them correctly and the other one is faking them ... well then it really doesn't mean much comparing them.

However, your hash rate shown on the web site of course is only based on valid, non-stale shares, so the hash rate is of course what matters.

Anyway,
The bitmain driver code used to "attempt" to intercept stale shares and discard them rather than pass them back to the main cgminer code.
i.e. it was hiding them so they weren't counted.
The main cgminer code of course should decide based on the cgminer options, not the bitmain driver.
That was one of the fixes I did to the S1 driver years ago when I first fixed the bitmain crappy code, that bitmain never copied any of the fixes.

Anyway, while perusing the bmminer driver code I felt the urge to run away screaming ...
Here's their latest function that screws around with the shares before passing them back to the main cgminer code ...
 https://github.com/bitmaintech/bmminer/blob/master/driver-btm-c5.c#L7887
Damn, who let those retard programmers at bitmain near a keyboard.
What it is supposed to do is simply retrun the nonce and let the main cgminer code check it properly, not all that screwing around they are doing there.

But that wasn't the reason for wanting to run away screaming ...
There is a function in all your recent bitmain miners "send_mac"
 https://github.com/bitmaintech/bmminer/blob/master/driver-btm-c5.c#L7764
It connects to bitmain
 https://github.com/bitmaintech/bmminer/blob/master/driver-btm-c5.c#L7683
Since AUTH_URL is:
 https://github.com/bitmaintech/bmminer/blob/master/driver-btm-c5.c#L223
"auth.minerlink.com"
and it sends your mac address, some miner id, and some hash board id string to bitmain
 https://github.com/bitmaintech/bmminer/blob/master/driver-btm-c5.c#L7774
Randomly every 1 to 11 minutes while the miner is running
 https://github.com/bitmaintech/bmminer/blob/master/driver-btm-c5.c#L7783
It doesn't matter what pool you are mining on, it still connects to bitmain

Now here's the real fun part ...
It checks for a reply from bitmain and if bitmain replies with anything containing the word "false"
 https://github.com/bitmaintech/bmminer/blob/master/driver-btm-c5.c#L7755
Then it will abort the checking function
 https://github.com/bitmaintech/bmminer/blob/master/driver-btm-c5.c#L7777
with the message "Stop mining!!!"
But if it fails to connect to bitmain or it doesn't get a "false" reply, it will continue checking randomly every 1 to 11 minutes connecting to bitmain.

Now I wonder why they would have a function like that, there in the code ... ... ... ... ...

Nice!  Keeping steady, I love it!

Got worse as at the last check I ran, this should hopefully make it a bit better.

Love it! I'd be interested in knowing, kano-san, how the s9v1 BDR is doing. Still abysmal and suspect?

Block! by Dsman
S9v1
1.6BTC txn fees

I'm curious, unreliable in what ways? I've used them since early 2014 and can't complain.

Only issue I've had is that within the past 2 weeks 2 tx for purchases and an xfr to Coinbase each took ~3days to confirm despite what should have been a decent TX fee paid each time.

He mines on the pool here and I have contact with Canaan so it's a good place to ask and he already got his answer

Also blockchain.info is unreliable

hmm, very new I guess but we were all there at one time.. They are talking about the transaction ID code or TxId. In your Bitcoin wallet check the status of the tx. That is where you will find the Tx Id.

After you do a BTC transaction a code is issued that identifies it in the Blockchain forever.  eg a2c8d0f9e9d6185cf5dd0383812e123d3e8f330b87b012de5eb58edacb08245f

That breaks out into https://blockchain.info/tx/a2c8d0f9e9d6185cf5dd0383812e123d3e8f330b87b012de5eb58edacb08245f for a s9 I bought.

 Also - you MUST tell Canaan that that you are using BTC. Reply to the email they sent with wire transfer info and tell them that you will be using BTC. They will reply with the BTC amount and address to send it to.

Lastly - this is the wrong thread/section for a question like this...

Yep it's a small botnet of around 500 computers using invalid usernames and trying to login.
I'm guessing it's just a spam attempt at the (separate) web server.

They've been doing it for about 1.5hrs so far with a small break in the middle.

But yep, the API is unaffected by it and it has no effect on mining at all.

Kinda what I figured, but thought I would check if others were experiencing it too.

Same here, it started in the last hour or so.

If you need some info, I think the API is still working.

Yes. That usually happens when Kano detects bots trying to connect to the pool.