KanoPool since 2014 🐈 - PPLNS and Solo 0.5% fee - Worldwide - 2438 blocks

[kano]

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.

[jeecom]

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

[AerialGopher]

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?

[kano]

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

[kremit]

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.

[AerialGopher]

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!

[AerialGopher]

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!

[DrSha]

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

[A.Delaney]

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!

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.

[jeecom]

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

I don't see the hashrate being affected unless it is a prolonged (meaning 6 months + ) BTC price decline.   It has to be long enough to discourage people from buying more miners or unplugging / selling existing ones.

[DrSha]

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!

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.

Look like global hashrate dropped last 12 hrs.  25ex to 23ex

https://imgur.com/a/e4ed9

[kano]

RE: proxy post further above

Basically what a proxy does is act like a normal miner to the pool.

The simple version of it is:
It adds to the size of coinbase1 and subtracts from the size the miner is allowed to use between coinbase1 and coinbase2
i.e. if it used 1 byte, it could send different work to 256 miners - each one would be given coinbase1 with X appended, coinbase2, and with the size between them now 1 byte smaller.
Each miner would, of course, get a unique X.

What this also means is that you will average 18 shares per minute between your proxy and the pool - even if you have 256 miners.
(of course the proxy can break it larger to 2 bytes=65536 miners, 3 bytes=16777216 miners etc)
So network load between you and the pool is lower with a proxy - it can be the equivalent of a single miner even if you have many thousands of miners.

How this looks in stratum would be:

From Pool to Proxy
When the proxy first connects to the pool, the pool tells it your ID and the enonce size
From then on you use those 2 for all work.
So work arrives like so:
{"params":["aabbccdd00001122","a83fb5dc201c2a484569c0cbba8b5b8e2e524e38002e4c590000000000000000",
"01000000010000000000000000000000000000000000000000000000000000000000000000fffff fff3603eebf0700042c11795a049cbb5e180c",
"0a2ef09f90882e12204b616e6f506f6f6c20283d4f2e4f3d2920ffffffff02a6507b55000000001 976a914370c9767eeb3f6add88c207733b7ff2e920622c888ac0000000000000000266a24aa21a9 ed73a4cfcddaecfbc3f77505bccccdc8ff4d13cdda8fd7d06347b61b68f48ac1d900000000",
["743b249690334d20a53686ee75981af35cbc2325e03e0114d8a3e19f98f14d37",...],
"20000000","176c2146","5a79112c",false],"id":null,"method":"mining.notify"}

From Proxy to miner XX
When the miner connects to the proxy it would get the same ID but with a shorter enonce value (1 shorter if configured for 256 miners)
Then each time the proxy gets work from the pool, it sends it to each miner with each miner's unique XX value.
{"params":["aabbccdd00001122","a83fb5dc201c2a484569c0cbba8b5b8e2e524e38002e4c590000000000000000",
"01000000010000000000000000000000000000000000000000000000000000000000000000fffff fff3603eebf0700042c11795a049cbb5e180cXX",
"0a2ef09f90882e12204b616e6f506f6f6c20283d4f2e4f3d2920ffffffff02a6507b55000000001 976a914370c9767eeb3f6add88c207733b7ff2e920622c888ac0000000000000000266a24aa21a9 ed73a4cfcddaecfbc3f77505bccccdc8ff4d13cdda8fd7d06347b61b68f48ac1d900000000",
["743b249690334d20a53686ee75981af35cbc2325e03e0114d8a3e19f98f14d37",...],
"20000000","176c2146","5a79112c",false],"id":null,"method":"mining.notify"}

The difference in the work is only the XX that's been added (and of course the initial connection being told the enonce is 1 byte smaller)
This means each miner is mining something different, but based off the same single work item.

[DrSha]

Thanks for the additional info on that kano. 

If I could give merit for that I would! 

[A.Delaney]

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!

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.

Look like global hashrate dropped last 12 hrs.  25ex to 23ex

https://imgur.com/a/e4ed9

I was going off the hashrate on BTC.com. It had dropped under 20Eh recently and popped back over 21Eh today. I just can’t see difficulty continuing to rise at the rate it has been. If this price stays. I think it’s going to put a hurtin on the big data centers that have 6 figure power bills.

[DrSha]

The Diff looks to me like it's been somehow "manipulated" to squeeze out the small.. (just a theory but plausible never the less)

[kano]

The Diff looks to me like it's been somehow "manipulated" to squeeze out the small.. (just a theory but plausible never the less)

The diff will always grow to suit large miners better than small miners.
It's even suggesting in the inital whitepaper by 'Satoshi' that that will be the case.
However, that is a simple economics concept, known as economies of scale.

[BSGMiner]

So, I felt the urge to ramble on about Bitcoin again...

And, thank you for it! Pretty awesome to get an explanation like that.

[clgrissom3]

So, I felt the urge to ramble on about Bitcoin again...

And, thank you for it! Pretty awesome to get an explanation like that.

That was a pretty cool ramble!

[VRobb]

Indeed, as the mighty Zep said, "ramble on!" 
And Mine On!   

[DrSha]

The Diff looks to me like it's been somehow "manipulated" to squeeze out the small.. (just a theory but plausible never the less)

The diff will always grow to suit large miners better than small miners.
It's even suggesting in the inital whitepaper by 'Satoshi' that that will be the case.
However, that is a simple economics concept, known as economies of scale.

That is true kano,

Though this may be the case we have seen what many see as attack on the network. (my thought's / speculation)

Lets assume a group wanted bitcoin all for themselves, How could they "secure" there investment and take control of the network without need for 51% attacks ect..

Step 1. make a new chain..

2. We saw the creation of a 2nd chain BCH now we know from this they created with something called "emergency diff adjustment" now  BCH chain is now slightly ahead of Bitcoin’s in size and block height.!  

"Block chain length" is calculated from the combined difficulty of all the blocks, not just the number of blocks in the chain. The one that represents the most computation will win

2. Now you have a 2nd chain to "jump" back and forth as you please.

Now I refer to a very early set of comments on the forum regarding "difficulty adjustment attack"

https://bitcointalk.org/index.php?topic=318727.0

Quote from user Rival

Any time that you intentionally throttle back your hash rate you lose... period.

Dozens of convoluted strategies have been formulated and tried and in all cases they screw you. The only effective way to manipulate the difficulty is by somehow sabotaging your competition so that THEY are the ones who are throttling back their hash rates.

There is no need to "throttle back" when they can mine there "fork" with difficulty adjustment to suit. this keeps the money rolling in while you throw hashrate on and off the original chain.

https://imgur.com/a/1AtFu

The jump and continued "fast" growth of the diff from 1st august is something people should really be looking into and asking questions.  The hashrate has been "far" from stable we see large chunks come and go from the chain in my view to "fuzz" the network into jumping + diff each time.   I am not alone in thinking this theory once you push the diff higher and higher squeezing out the home miners "even with multiple s9's (which in most country's now take around 400+ days ROI give or take depending on electrical rates) and they are not losing money in the process by having the separate chain to mine on.  This relinquishes the need to throttle back and lose money in the process.

this is not fact so please do not take it as such its more "speculation".    But is possible..