Author

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

legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Workers > Shift Graph   put "all" without quotes in input box, make sure it's checked and hit update

Edit: if you mean for the whole pool Pool > Graph

I should have clarified: I mean without an account, just anonymous mining with an address (like was possible with eligius).
If you want details then use an account.
... as it says on the http://kano.is/ web page Smiley
If you address mine, you just get the stats available at the time you check them.

Right ok. Could you provide accurate figures, not just rounded to 1Th/s? Say 2 significant figures or similar? Thanks.
It's 3 significant figures.
member
Activity: 81
Merit: 10
Workers > Shift Graph   put "all" without quotes in input box, make sure it's checked and hit update

Edit: if you mean for the whole pool Pool > Graph

I should have clarified: I mean without an account, just anonymous mining with an address (like was possible with eligius).
If you want details then use an account.
... as it says on the http://kano.is/ web page Smiley
If you address mine, you just get the stats available at the time you check them.

Right ok. Could you provide accurate figures, not just rounded to 1Th/s? Say 2 significant figures or similar? Thanks.
full member
Activity: 233
Merit: 100
reality is what you think it is
Edited, solved the issue, no need to answer the question that was in this place.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Stale block Sad
Came in just after the block change.
CKDB automatically switches it to 'orphan' if the current block we are working on isn't the block we got.
i.e. the main pool bitcoind had switched to a different block before that block was processed, thus it was stale.

Edit: to be specific:
The other pool's block arrived at 2017-03-07 13:06:08.989605 UTC and bitcoind had processed it by 2017-03-07 13:06:09.156078 UTC
(166ms to fully process the block)
However, the share arrived at 2017-03-07 13:06:09.256 so it was 100ms after the block had changed - so when ckpool submitted it, bitcoind said 'no thanks' - thus CKDB marked it as an orphan since we weren't working on the share's block, and I then flagged it as 'Stale'
As usual, CKDB shows all block attempts by ckpool, if they succeed or fail.
full member
Activity: 233
Merit: 100
reality is what you think it is
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4

@Kano any though of supporting Bitcoin Unlimited?
Well they seem to be the closest to what the pools and miners in general want, but as I mentioned in the Antpoo thread, core seems to be the centralised control of bitcoin at the moment so it would need a core option to vote for it.

We had over 70% support for BIP100 that would almost certainly have got more support, but since core didn't want it, the minority centralised control (core) got their wish, no BIP100.

The biggest problem with the whole blocksize issue is that everyone has an agenda to add to it, core being the worst in this situation.

A simple vote for a simple blocksize increase (not the ridiculous BIP101 version) would get in very quickly and then the rest of the rubbish being peddled by everyone could be ignored Tongue
It seems no one will do that, as I said, everyone has some other agenda they want.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Workers > Shift Graph   put "all" without quotes in input box, make sure it's checked and hit update

Edit: if you mean for the whole pool Pool > Graph

I should have clarified: I mean without an account, just anonymous mining with an address (like was possible with eligius).
If you want details then use an account.
... as it says on the http://kano.is/ web page Smiley
If you address mine, you just get the stats available at the time you check them.
member
Activity: 81
Merit: 10
Workers > Shift Graph   put "all" without quotes in input box, make sure it's checked and hit update

Edit: if you mean for the whole pool Pool > Graph

I should have clarified: I mean without an account, just anonymous mining with an address (like was possible with eligius).
jr. member
Activity: 74
Merit: 1

@Kano any though of supporting Bitcoin Unlimited?
newbie
Activity: 49
Merit: 0
Workers > Shift Graph   put "all" without quotes in input box, make sure it's checked and hit update

Edit: if you mean for the whole pool Pool > Graph
member
Activity: 81
Merit: 10
Thanks kano for your pool! Seems like a good place. I am struggling though, unable to get some basic stats apart from the current (very rounded) hashrate. A simple graph like eligius had would be nice to have and give some piece of mind about past performance. I also have not yet quite worked out the payout scheme and any minimas. Where may I read up on that?

You could abuse cacti to draw monthly and/or weekly graphs based on data from your address.php - if this data were more accurate and parseable, it is also something that user may do herself. I can offer to do this locally if you make the data accessible and you could then implement it in the pool?
member
Activity: 81
Merit: 10

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 ... ... ... ... ...

kano, would this give them the capability to remotely shutdown one's miner? For now it's just logging but if this condition works, who knows what else they will extend it to.

and if that day comes, maybe I have to block such connection on the router?
Well the real issue related to that is: what code do they actually have in the miner?
As it is in git, it's effectively benign, just possible (with a minor DNS change) to have every recent Bitmain miner log information to Bitmain.

They delayed creating the git beyond the license requirements (even though creating the git is a few minutes effort)
Who knows what they're up to Tongue

Blocking it isn't trivial.
Updating the hosts file as suggested above by bitsink will block it until a power cycle.

I beg to differ: The hosts file DOES survive a power cycle (at least on a S9 13.5TH model wih the XILINX controller), but would not survive a hard reset without a hack... but obviously this is only a hack. What is the longterm solution? It must be possible to use a different miner all together with the right driver / interface if this is documented?
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
Hmm, just had a thought: When I got my 1st Avalon 721's I had Antpool as my #3 failover. The Avalons could not connect to it. Think Bitmain might use that code to identify if their product is connected to the pool? Last time I ran my rare A1 Dragon clone from AMT it connected but that was around 2 yrs ago... (and truthfully Antpoo not liking Avalons does not break my heart)
Well, firstly they'd have to have a DNS A record - which I don't check that address, but I gather it may usually not exist.

They can just look at the agent information you supply when you connect to the pool and be pretty sure it's a Bitmain miner, if it's directly connected to the pool, so I doubt they'd bother doing that.

If it was a proxy of miners, then there's all sorts of issues about if any of the miners can get out to the net, how many there are vs the hash rate, etc.

All in all, pretty pointless.
legendary
Activity: 3822
Merit: 2703
Evil beware: We have waffles!
Hmm, just had a thought: When I got my 1st Avalon 721's I had Antpool as my #3 failover. The Avalons could not connect to it. Think Bitmain might use that code to identify if their product is connected to the pool? Last time I ran my rare A1 Dragon clone from AMT it connected but that was around 2 yrs ago... (and truthfully Antpoo not liking Avalons does not break my heart)
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4

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 ... ... ... ... ...

kano, would this give them the capability to remotely shutdown one's miner? For now it's just logging but if this condition works, who knows what else they will extend it to.

and if that day comes, maybe I have to block such connection on the router?
Well the real issue related to that is: what code do they actually have in the miner?
As it is in git, it's effectively benign, just possible (with a minor DNS change) to have every recent Bitmain miner log information to Bitmain.

They delayed creating the git beyond the license requirements (even though creating the git is a few minutes effort)
Who knows what they're up to Tongue

Blocking it isn't trivial.
Updating the hosts file as suggested above by bitsink will block it until a power cycle.
But you don't know what the actual address will be, so you can't block that IP in advance at your router as such without whitelisting instead.
sr. member
Activity: 441
Merit: 250
No zuo no die why you try, u zuo u die dont be shy

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 ... ... ... ... ...

kano, would this give them the capability to remotely shutdown one's miner? For now it's just logging but if this condition works, who knows what else they will extend it to.

and if that day comes, maybe I have to block such connection on the router?
hero member
Activity: 1092
Merit: 552
Retired IRCX God
Ja. Especially considering how much Bitmain has dicked around with a plethora of Firmware updates...
Most of that was in a vain attempt to strike a balance between how a high-performance miner should operate and how hobbits, running it 4' from their bed, want it to run.
legendary
Activity: 952
Merit: 1003
Seriously would anyone think there was only the one original commit and only one change ever since that? Smiley
Of course no one (with a pulse) believes that. I'm not exactly happy with how all that came down with Con, but it's not my "stuff" (thankfully) and given my former profession, that's a blessing (for me, at least). Anyway...that sequence of events (which happened to include you as collateral damage, it seems to me) is what led me to mine only here, and to not buy Bitmain gear again. I don't sleep a heckuva lot anyway, but choices like these at least make those power naps a lot more peaceful.

Mine on.  Kiss
legendary
Activity: 3822
Merit: 2703
Evil beware: We have waffles!
Ja. Especially considering how much Bitmain has dicked around with a plethora of Firmware updates...

I know I certainly wonder Bitmain did with their software in latest R4 and s9's. Looking at hash rate reported by Awesome miner shows a very uncharacteristic smoothness vs what I normally see from s7's and earlier s9's. Think it's a s9 b22 I have at work that displays like the R4's do.

This shows my 2 R4's and Batch-1/b3 s9's at home. No way in hell are the R4's performing THAT evenly. BMminer 2.0 must be doing major stats smoothing of some sort and given that, who knows what else.
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
re: https://bitcointalksearch.org/topic/m.18083086 (s9's phoning home?)
Since you just brought up He Who Is Not To Be Named, I do have to mention that he found that bit of code last year. As far as he could tell it did not actually do anything but one of his mods was to remove the code.. However, still worrying though...

My take on the code: If folks here remember, think it started with the s4 and was definitely in at least the early s5's. Bitmain for a time looked at a central Cloud control/monitoring solution for us using their miners. The site name? Minerlink.com In the Bitminer GUI they had a tick-box to use that service.

Don't think they ever took it active outside China. Just looked and the site is still there but have not seen that tickbox on any s9 or s7 as far as I can recall. Hmm.

Question still remains, is that code benign and just unused legacy? Considering how much Bitmain says they re-wrote all the code in the s9's ya gotta wonder how that got left in...
The code does exactly as I stated, my running commentary and links are not guesses Smiley
Although -ck threw me off the ckpool and cgminer team for stating that I have a lot of experience
(I also have more than him - but his medical god status got upset at that comment and he threw a public tantrum about it)
I do know more about coding/programming than most.

The code in git is benign if bitmain keeps the DNS A record missing as it currently is.
It's only a one line change to their DNS to enable and disable it.
When you enable a missing DNS A record it is usually an almost immediate activation.

However, the git vs the code running in your Bitmain miners ... there's certainly no guarantee that's exactly the same either.
The git shows one inital commit and one change since then.
Seriously would anyone think there was only the one original commit and only one change ever since that? Smiley
Jump to: