KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 494.

A.Delaney

member

Activity: 266

Merit: 13

Quote from: AerialGopher on February 05, 2018, 09:02:23 PM

Hashrate 21.00 EH/s
Difficulty 2,603,077,300,218 - 2.60 T

Next Difficulty Estimated
(+11.05%) 2.89 T

Date to Next Difficulty
0 Days 22 Hours

NOOOOOOOOOOOOOOOOOOOOOOOO Make it stop! Sad

The hashrate actually came back up a little bit. I’m hoping with the downward trend in the BTC price that difficulty will reverse at some point.

DrSha

jr. member

Activity: 42

Merit: 4

<3 BTC

Hey NewKo!

I saw your post mining I went to send you this in a PM but as I am new there was filter out "noob" block on the pm system. I would like to share with you some things I have learned about the process.

Here is a copy of a stratum proxy log I use to solo mine it shows what the miner is requesting and what it is submitting.

It really helped me to see what the miner is doing and what info is being passed from the miner to the pool and vice versa.

breakdown:

1. Header - This is the block header submitted from pool to miner.
2. Coinbase1 / Coinbase2 - The pool has to send coinbase1 and coinbase2 to the miners
3. Prevhash - The previous block hash
3. The miner the gets some other info like Nbit, Ntime, and the Merkle root.

then the miner starts to hash the info. after some time if no solution is found the miner will get the follwowing update and "move on" to the next

Hash on proxy 1 has changed to 000000000000000000343339f5f13bd42af98000229c35ee99d7386876be65b6
Hash on proxy 0 has changed to 000000000000000000343339f5f13bd42af98000229c35ee99d7386876be65b6

and the process continues

I hope this helps the visual representation really helped me understand I now log all my shares from my miners via proxy it's gives a whole new perspective and lets you watch real time what your miner is doing.

Code:

[2018-02-03 18:56:18.409] Json found jobid: 4
[2018-02-03 18:56:18.409] Header: 2000000072c559e18a8cc8a1f5a075f54dfa90c1b578553f00380326000000000000000000000000000000000000000000000000000000000000000000000000000000005a7605d2176c2146000000000000008000000000000000000000000000000000000000000000000000000000
[2018-02-03 18:56:18.409] Proxy 1:0 broadcast updated
[2018-02-03 18:56:18.409] Stratifier received request: diff={"proxy": 1, "subproxy": 0, "diff": 4000.0}
[2018-02-03 18:56:18.409] Update diff: {"proxy": 1, "subproxy": 0, "diff": 4000.0}
[2018-02-03 18:56:18.409] Json found entry proxy: 1
[2018-02-03 18:56:18.409] Json found entry subproxy: 0
[2018-02-03 18:56:18.409] Got updated diff for proxy 1:0
[2018-02-03 18:56:18.428] Proxy 0:0 received method mining.notify
[2018-02-03 18:56:18.428] Received new notify from proxy 0:0
[2018-02-03 18:56:18.428] JobID 5a71009a000017f7
[2018-02-03 18:56:18.428] Coinbase1 01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff350351be070004d205765a0494f067160c
[2018-02-03 18:56:18.428] Coinbase2 0a636b706f6f6c112f736f6c6f2e636b706f6f6c2e6f72672fffffffff036bf2664e000000001976a914397a65cdbbbf16e6cb3etb440060644171a1959488aca1bcca00000000001976a914f4cbe6c6bb3a8535c963169c22963f3a20e7686988ac0000000000000000266a24aa21a9edb22d319ba7121a418dc8f816a95a0bec2457a283f81f7fae88da910ad2f0d3c000000000
[2018-02-03 18:56:18.428] Prevhash 72c559e18a8cc8a1f5a075f54dfa90c5b578553f003802560000000000000000
[2018-02-03 18:56:18.428] BBVersion 20000000
[2018-02-03 18:56:18.428] Nbit 176c2146
[2018-02-03 18:56:18.428] Ntime 5a7605d2
[2018-02-03 18:56:18.428] Clean false
[2018-02-03 18:56:18.428] Merkles 11
[2018-02-03 18:56:18.428] Merkle 0 c7e1d9dcaca5d7cf50de92be6cf56cd386cd1a317231b705df3b4c832b517125
[2018-02-03 18:56:18.428] Merkle 1 eb49f18d7bd2f166eefff8802516f6c8cb8dd7d214176d4235add037370be835
[2018-02-03 18:56:18.428] Merkle 2 1456852b0d4de918c40f8390e27deeb493a05a234c1df5587e33360f27708161
[2018-02-03 18:56:18.428] Merkle 3 506f2121f16ddc672ea3dec2719d54d386d15eae59a60dc4860ec001f934e0d8
[2018-02-03 18:56:18.428] Merkle 4 14c75427ed1bec55e637b869ff6759759c0dc5092b37ac61d90069e19cc4ca8a
[2018-02-03 18:56:18.428] Merkle 5 084a6e35265e5dd498f058cb948eb32024a095f4f3537187f625f305121460ec
[2018-02-03 18:56:18.428] Merkle 6 9cb85c0f564b5ad595ac5cefdca5489a090ff04943d98490babdcb755058895c
[2018-02-03 18:56:18.428] Merkle 7 f9a36f8c9ea52fe601f6fac4d0342413c0276b14a392e543a97ed45dbed8885b
[2018-02-03 18:56:18.428] Merkle 8 ba867d1fa19c8ab02588a94a20aa4a23df2360d9b8b4982e5b333f4f964cabc7
[2018-02-03 18:56:18.428] Merkle 9 cd453fd13686319ba7fdbcf3cce7e7105f5742990a00c75d07f2b13467c863e3
[2018-02-03 18:56:18.428] Merkle 10 458de899b5b81f6b8faedba931859c1ee89756cfe6e6cba3abd019a2ca18e811
[2018-02-03 18:56:18.428] Select timed out in read_socket_line
[2018-02-03 18:56:18.428] Stratifier received request: notify={"proxy": 0, "subproxy": 0, "jobid": 5, "prevhash":
[2018-02-03 18:56:18.429] Proxy 0:0 broadcast updated stratum notify without clean
[2018-02-03 18:56:18.429] Stratifier received request: diff={"proxy": 0, "subproxy": 0, "diff": 4000.0}
[2018-02-03 18:56:18.429] Update diff: {"proxy": 0, "subproxy": 0, "diff": 4000.0}
[2018-02-03 18:56:18.429] Json found entry proxy: 0
[2018-02-03 18:56:18.429] Json found entry subproxy: 0
[2018-02-03 18:56:18.429] Got updated diff for proxy 0:0
[2018-02-03 18:56:18.469] Accepted client 3 share diff 1328.7/42/4K: 000000000031522279e455b1eeb364b1c9366cfa0cdb4a0a6c28a2cf98096333
[2018-02-03 18:56:18.470] Sending stratum message share.result
[2018-02-03 18:56:18.796] Accepted client 2 share diff 1006.3/42/4K: 0000000000411fee4e15b9ea0a0383ceb7b334aa513006e67cca17732df220c9
[2018-02-03 18:56:18.797] Sending stratum message share.result
[2018-02-03 18:56:18.840] Accepted client 7 share diff 47.3/42/4K: 00000000056a9a6af9c6d6c75cc48229f6b85e4959606c2dbd567602bec33d4d
[2018-02-03 18:56:18.841] Sending stratum message share.result
[2018-02-03 18:56:18.841] Accepted client 7 share diff 288.5/42/4K: 0000000000e3284ef365f208fd2d7b564ba20242f376518e5a53b283bee82966
[2018-02-03 18:56:18.841] Sending stratum message share.result

AerialGopher

jr. member

Activity: 196

Merit: 4

Hashrate 21.00 EH/s
Difficulty 2,603,077,300,218 - 2.60 T

Next Difficulty Estimated
(+11.05%) 2.89 T

Date to Next Difficulty
0 Days 22 Hours

NOOOOOOOOOOOOOOOOOOOOOOOO Make it stop! Sad

AerialGopher

jr. member

Activity: 196

Merit: 4

Ahh but the 30 seconds of relative silence i got while the two in my office rebooted was.... like beautiful. I have not heard that silence since Nov 21, 2017.. when I first plugged it in and went OMFG!!!! I cant stand it!

Its in a box now ith another one, sound proofed a little. So its not as bad. Its like one pf them LOUD IBM servers I used to have. I just put everyone on speakerphone that calls me, and they get to experience it too!!!
HA!

kremit

newbie

Activity: 23

Merit: 0

Quote from: AerialGopher on February 05, 2018, 06:57:16 PM

Quote from: kano on February 05, 2018, 06:45:53 PM

Well actually

(no not the maths)
When you reboot a miner it gets a new unique number that's in the coinbase sig as I mentioned in that long post.
So it does actually change your hash results

Of course it's random ... but it does change it.

So, in theory, the newly generated hash might be what ends up solving a block? maybe the old one is worn out... :-) Its like playing the same lottery numbers over and over again? but I just changed the lotto numbers?

In theory, yes. On the other hand, the pool sends you new "lottery numbers" (approximately) 3 times per minute... and there's the peculiar situation that there's an extremely small but finite chance ("So you're saying there's a chance?") that the next block could have been hiding a few trillion numbers away in the nonce that was being used before you rebooted.

Rebooting would probably be more beneficial if you were worried there was some sort of hardware issue where chips or memory weren't rolling properly.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: AerialGopher on February 05, 2018, 06:57:16 PM

Quote from: kano on February 05, 2018, 06:45:53 PM

...
Well actually

(no not the maths)
When you reboot a miner it gets a new unique number that's in the coinbase sig as I mentioned in that long post.
So it does actually change your hash results

Of course it's random ... but it does change it.

So, in theory, the newly generated hash might be what ends up solving a block? maybe the old one is worn out... :-) Its like playing the same lottery numbers over and over again? but I just changed the lotto numbers?

Well as I said it's random.
The effect can be positive or negative - it's random.
But it does have an effect - that you can't predict.

AerialGopher

jr. member

Activity: 196

Merit: 4

Quote from: kano on February 05, 2018, 06:45:53 PM

Quote from: AerialGopher on February 05, 2018, 06:33:39 PM

Quote from: jeecom on February 05, 2018, 06:30:54 PM

Quote from: AerialGopher on February 05, 2018, 06:22:24 PM

Ahh, I don't know why.. but I am going to reboot my 7 S9's. I did that before, and then the pool found a block.. I Know... its useless step, but I have a hunch...

Some have been up for 29 days.

I will sacrifice my .00001% of shares for this... then you will see a block will be busted!

I rebooted mine earlier today for the same reason!

Might help, There might be some bad firmware issue that no one has found, and long uptimes cause.

I was more worried about Kano actually working out the math on 5 minutes of 7 S9's and the share value not being .00001% :-) I just threw a number out... No need to calculate it - I know you love math... :-) haha

Well actually

(no not the maths)
When you reboot a miner it gets a new unique number that's in the coinbase sig as I mentioned in that long post.
So it does actually change your hash results

Of course it's random ... but it does change it.

So, in theory, the newly generated hash might be what ends up solving a block? maybe the old one is worn out... :-) Its like playing the same lottery numbers over and over again? but I just changed the lotto numbers?

jeecom

jr. member

Activity: 56

Merit: 1

Quote from: kano on February 05, 2018, 06:45:53 PM

....
Well actually

(no not the maths)
When you reboot a miner it gets a new unique number that's in the coinbase sig as I mentioned in that long post.
So it does actually change your hash results

Of course it's random ... but it does change it.

They way I look at it is there are two possibilities. We get a block soon, and then we can feel validated that we did something to help. We don't get a block soon, and then it doesn't matter.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: AerialGopher on February 05, 2018, 06:33:39 PM

Quote from: jeecom on February 05, 2018, 06:30:54 PM

Quote from: AerialGopher on February 05, 2018, 06:22:24 PM

Ahh, I don't know why.. but I am going to reboot my 7 S9's. I did that before, and then the pool found a block.. I Know... its useless step, but I have a hunch...

Some have been up for 29 days.

I will sacrifice my .00001% of shares for this... then you will see a block will be busted!

I rebooted mine earlier today for the same reason!

Might help, There might be some bad firmware issue that no one has found, and long uptimes cause.

I was more worried about Kano actually working out the math on 5 minutes of 7 S9's and the share value not being .00001% :-) I just threw a number out... No need to calculate it - I know you love math... :-) haha

Well actually

(no not the maths)
When you reboot a miner it gets a new unique number that's in the coinbase sig as I mentioned in that long post.
So it does actually change your hash results

Of course it's random ... but it does change it.

AerialGopher

jr. member

Activity: 196

Merit: 4

Quote from: jeecom on February 05, 2018, 06:30:54 PM

Quote from: AerialGopher on February 05, 2018, 06:22:24 PM

Ahh, I don't know why.. but I am going to reboot my 7 S9's. I did that before, and then the pool found a block.. I Know... its useless step, but I have a hunch...

Some have been up for 29 days.

I will sacrifice my .00001% of shares for this... then you will see a block will be busted!

I rebooted mine earlier today for the same reason!

Might help, There might be some bad firmware issue that no one has found, and long uptimes cause.

I was more worried about Kano actually working out the math on the downtime of 5 minutes of 7 S9's and the share value not being .00001% :-) I just threw a number out... No need to calculate it - I know you love math... :-) haha

minergain.com

member

Activity: 285

Merit: 10

Free mining equipment tracking and reporting

Quote from: jeecom on February 05, 2018, 06:30:54 PM

I rebooted mine earlier today for the same reason!

Ok, I'm convinced. Mine are rebooting now too after 25 days.. Here we go!

jeecom

jr. member

Activity: 56

Merit: 1

Quote from: AerialGopher on February 05, 2018, 06:22:24 PM

Ahh, I don't know why.. but I am going to reboot my 7 S9's. I did that before, and then the pool found a block.. I Know... its useless step, but I have a hunch...

Some have been up for 29 days.

I will sacrifice my .00001% of shares for this... then you will see a block will be busted!

I rebooted mine earlier today for the same reason!

rifleman74

member

Activity: 658

Merit: 21

4 s9's 2 821's

Quote from: heartlandmining on February 05, 2018, 06:27:55 PM

Quote from: DPoS2 on February 05, 2018, 06:13:15 PM

This place has turned into a social experiment more than a mining operation

The social experiments currently taking place at other pools* are the reasons why we're here now.

* Which can certainly be backed up by the mathematics.

That's going to leave a mark!

heartlandmining

jr. member

Activity: 104

Merit: 5

Quote from: DPoS2 on February 05, 2018, 06:13:15 PM

This place has turned into a social experiment more than a mining operation

The social experiments currently taking place at other pools* are the reasons why we're here now.

* Which can certainly be backed up by the mathematics.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: DPoS2 on February 05, 2018, 06:13:15 PM

Quote from: kano on February 05, 2018, 05:47:38 PM

Profitability is the same at most pools.
While we are 'expected' to find multiple blocks per diff change, i.e. multiple blocks per 2 weeks, profitability wont be affected much by changing pools.
You can't predict luck and luck is the biggest factor in PPLNS.

Of course if the pool gets 'too' small then that will noticeable affect Profitability, a fact that certain smaller pools like to hide from their miners, however we've been growing pretty well over the last month ... so that's not currently a concern.

It already got too small as soon as you dropped to less than 20 blocks per month expected. That's pretty much the minimum amount of chances to avoid what is going on right here. You can't ignore time frames when you get small and try to relate a diff% in your current state with when you had a much higher expected block %

This place has turned into a social experiment more than a mining operation

So ... can you back up that comment with maths?

AerialGopher

jr. member

Activity: 196

Merit: 4

Ahh, I don't know why.. but I am going to reboot my 7 S9's. I did that before, and then the pool found a block.. I Know... its useless step, but I have a hunch...

Some have been up for 29 days.

I will sacrifice my .00001% of shares for this... then you will see a block will be busted!

DPoS2

member

Activity: 189

Merit: 11

Quote from: kano on February 05, 2018, 05:47:38 PM

Profitability is the same at most pools.
While we are 'expected' to find multiple blocks per diff change, i.e. multiple blocks per 2 weeks, profitability wont be affected much by changing pools.
You can't predict luck and luck is the biggest factor in PPLNS.

Of course if the pool gets 'too' small then that will noticeable affect Profitability, a fact that certain smaller pools like to hide from their miners, however we've been growing pretty well over the last month ... so that's not currently a concern.

It already got too small as soon as you dropped to less than 20 blocks per month expected. That's pretty much the minimum amount of chances to avoid what is going on right here. You can't ignore time frames when you get small and try to relate a diff% in your current state with when you had a much higher expected block %

This place has turned into a social experiment more than a mining operation

rifleman74

member

Activity: 658

Merit: 21

4 s9's 2 821's

Quote from: CryptoSol on February 05, 2018, 05:35:37 PM

Question....

As I understand it this is the longest streak ever without finding a block in this pool. Is this purely because of bad luck or is it a combination of that and the recent difficultly increase?

If the latter, is this pool going to be profitable at it's current hash rate as these streaks become more prolonged and extend across additional difficulty increase events?

Partly a combo of all.

wavelengthsf

full member

Activity: 658

Merit: 118

I'm going to say we hit a block tonight before midnight eastern US time.

I think some of the wings I sacrificed yesterday took time to work their magic.

fjtropepe

member

Activity: 126

Merit: 10

Quote from: A.Delaney on February 05, 2018, 04:20:46 PM

This is like watching paint dry.

More like watching the pool water evaporate out of the pool. Paint dries much quicker than this.

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