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

[d57heinz]

but the time the machine takes to submit that diff one share is much faster than the diff 1 billion share..

Not sure what you are using to draw this conclusion, but a share is a share it a share - they all take the same "time to submit".  Submitting shares isn't what solves a block, it's how many SHA256 hashes per second that can be calculated.  There are no "secret settings" that increase your chances at solving a block.

Thats what i was getting at.. Just wondered if we had double the work if it gave us an advantage in anyway.... I always see the saying that every share has equal opportunity to solve a block.. So i just figured if your able to double the amount of shares you submit.. Albeit half the stratum diff would be required but each share has that chance to solve.. Im prolly way off here. Thanks for the help on this aswell

Best Regards
d57heinz

[wolfen]

Took out three of my miners on the flip

[jonnybravo0311]

but the time the machine takes to submit that diff one share is much faster than the diff 1 billion share..

Not sure what you are using to draw this conclusion, but a share is a share it a share - they all take the same "time to submit".  Submitting shares isn't what solves a block, it's how many SHA256 hashes per second that can be calculated.  There are no "secret settings" that increase your chances at solving a block.

Thats what i was getting at.. Just wondered if we had double the work if it gave us an advantage in anyway.... I always see the saying that every share has equal opportunity to solve a block.. So i just figured if your able to double the amount of shares you submit.. Albeit half the stratum diff would be required but each share has that chance to solve.. Im prolly way off here. Thanks for the help on this aswell

Best Regards
d57heinz

There is no advantage.  Your miners are hashing at X million/billion/trillion hashes per second.  Each one of those could potentially solve a block.  The vast majority of those hashes are thrown out because they are worthless (i.e. they don't even meet the difficulty 1 target).  When your miner actually does hit a diff 1 share, it is then the mining software that ignores it based upon the difficulty set by the pool.  If that share happens to exceed the target difficulty, then it is submitted to the pool.  If by chance that share also happens to exceed the target network difficulty, then the pool submits the block.

[d57heinz]

but the time the machine takes to submit that diff one share is much faster than the diff 1 billion share..

Not sure what you are using to draw this conclusion, but a share is a share it a share - they all take the same "time to submit".  Submitting shares isn't what solves a block, it's how many SHA256 hashes per second that can be calculated.  There are no "secret settings" that increase your chances at solving a block.

Thats what i was getting at.. Just wondered if we had double the work if it gave us an advantage in anyway.... I always see the saying that every share has equal opportunity to solve a block.. So i just figured if your able to double the amount of shares you submit.. Albeit half the stratum diff would be required but each share has that chance to solve.. Im prolly way off here. Thanks for the help on this aswell

Best Regards
d57heinz

There is no advantage.  Your miners are hashing at X million/billion/trillion hashes per second.  Each one of those could potentially solve a block.  The vast majority of those hashes are thrown out because they are worthless (i.e. they don't even meet the difficulty 1 target).  When your miner actually does hit a diff 1 share, it is then the mining software that ignores it based upon the difficulty set by the pool.  If that share happens to exceed the target difficulty, then it is submitted to the pool.  If by chance that share also happens to exceed the target network difficulty, then the pool submits the block.

Ahh yes.. ok that is what i needed. That makes sense.. Thank you.. I should have known that or been able to come to that conclusion. Brain fart..   I just thought that maybe working on more jobs could help it more. but i see now that doesn't do a thing . i def get it now.. Thanks again

Best Regards
d57heinz

[jonnybravo0311]

No problem.  Glad to help.

[vortexz]

pool just went dead and kano.is is down. Everything all right?

Nope, a ddos happening ...

will it be fixed soon ?

[not.you]

Took out three of my miners on the flip

One of mine completely flaked out.  Failed over to backup pool ok but then when it tried to fail back to kano even the web interface got all horked. S-7 batch 8.  I had to power cycle it.

[not.you]

pool just went dead and kano.is is down. Everything all right?

Nope, a ddos happening ...

will it be fixed soon ?

I got some shares in for a second there but looks like I failed over to backup again.

[CapnBDL]

Yeah...me too. I hate mining to my backup pool. It just seems like such a waste.

CapnBDL
     

[baazju]

Still no luck here :/ Site says mining all okay but still dead for me.

[PPOC]

Took out three of my miners on the flip

One of mine completely flaked out.  Failed over to backup pool ok but then when it tried to fail back to kano even the web interface got all horked. S-7 batch 8.  I had to power cycle it.

Same here, took out a batch 8 S7, does not reposed and can't ping. I'm not local to it, so could be a day out so before I can power cycle it. Bummer

[aarons6]

Took out three of my miners on the flip

One of mine completely flaked out.  Failed over to backup pool ok but then when it tried to fail back to kano even the web interface got all horked. S-7 batch 8.  I had to power cycle it.

Same here, took out a batch 8 S7, does not reposed and can't ping. I'm not local to it, so could be a day out so before I can power cycle it. Bummer

i bet bitmain used the same crappy bugged cgminer for the s7 that they used for all the other models...

[LoneRangir]

Yeah...me too. I hate mining to my backup pool. It just seems like such a waste.

CapnBDL
     

Two  of my three miners failed over properly , but all the shares of the third are being rejected.

[sorry2xs]

has anybody fail back yet

[e46btc]

S7 with December firmware switched to backup with no probs, no actions required.

[Prelude]

My B8 also shit the bed. Fucking garbage company that bitmain is.... Why can't they get software right?  

[kano]

OK, everthing should be all good now ... I'll update this post with more details shortly ...

[sorry2xs]

What good is ddos mitigation if doesn't work

[d57heinz]

My B8 also shit the bed. Fucking garbage company that bitmain is.... Why can't they get software right?  

it is odd that they would change up ck cgminer when it works fine without modification. Maybe someone here knows why they would do such a thing??  My thought are the crappy controller they use cant handle full version cgminer. any thoughts?

Best Regards
d57heinz

[not.you]

but the time the machine takes to submit that diff one share is much faster than the diff 1 billion share..

Not sure what you are using to draw this conclusion, but a share is a share it a share - they all take the same "time to submit".  Submitting shares isn't what solves a block, it's how many SHA256 hashes per second that can be calculated.  There are no "secret settings" that increase your chances at solving a block.

Thats what i was getting at.. Just wondered if we had double the work if it gave us an advantage in anyway.... I always see the saying that every share has equal opportunity to solve a block.. So i just figured if your able to double the amount of shares you submit.. Albeit half the stratum diff would be required but each share has that chance to solve.. Im prolly way off here. Thanks for the help on this aswell

Best Regards
d57heinz

There is no advantage.  Your miners are hashing at X million/billion/trillion hashes per second.  Each one of those could potentially solve a block.  The vast majority of those hashes are thrown out because they are worthless (i.e. they don't even meet the difficulty 1 target).  When your miner actually does hit a diff 1 share, it is then the mining software that ignores it based upon the difficulty set by the pool.  If that share happens to exceed the target difficulty, then it is submitted to the pool.  If by chance that share also happens to exceed the target network difficulty, then the pool submits the block.

Ahh yes.. ok that is what i needed. That makes sense.. Thank you.. I should have known that or been able to come to that conclusion. Brain fart..   I just thought that maybe working on more jobs could help it more. but i see now that doesn't do a thing . i def get it now.. Thanks again

Best Regards
d57heinz

The only thing submitting shares that are not blocks is doing is proving to the pool that you have a certain amount of hashrate working on finding bocks so you can be compensated for your efforts.  If you have a lot of hashrate then it doesn't make sense to have you submit difficulty 1 shares because it just creates a lot of unnecessary traffic to the mining server.  So the more hashrate you have, the more often you can submit higher difficulty shares.  So the mining server strikes a balance and figures out how high the difficulty should be in order to have you submit the desired number of shares in a given period of time.

The difficulty refers to the number of leading zeros on the hash.  If you look at a block hash like this for instance: https://blockchain.info/block-index/1004980
You see a bunch of zeros on the front of the hash (looks like about 17 right now).  When you generate hashes the actual hash is more or less random so the odds of having a lot of zeros on the front is low.  The more zeros you require at the front the lower the odds get of finding a hash like that (hence the difficulty).  It's not technically all zeros, otherwise difficulty jumps would be fixed numbers but you get the idea.  In order to prove to the pool that my miners are working and that I have a given amount of hashrate I may submit shares that have 7 leading zeros for example, depending on what difficulty my miners are working at.

The reason a pool doesn't really know your hashrate and that it can appear off on the pool side is because the pool just uses the number of shares you submit of a given difficulty over a given period of time to calculate your hashrate.  Then it pays you based on that calculation.  But since hashes are more or less random sometimes your miner might find more or less of a given difficulty share in a given period of time.  Long term those fluctuations even out.  Working at a lower difficulty would even out those fluctuations but create more traffic to the mining server.  Working at a higher difficulty would reduce traffic to the server but create even greater fluctuations in the calculated hashrate.  So the mining server needs to find the sweet spot in terms of what difficulty is best to set an acceptable amount of traffic and still allow a fairly accurate measure of your real hashrate.