Why 65536? Why this *constant*?
https://www.google.com/#q=2%5E16&safe=off
If you haven't already, you should try mining. That's the best way to learn.
Topic: Understanding difficulty - page 2. (Read 1906 times)
Why 65536? Why this *constant*?
https://www.google.com/#q=2%5E16&safe=off
If you haven't already, you should try mining. That's the best way to learn.
Quote
dunno i'm very tired
But will you be back tomorrow to this question?
Thanks.
OK, I get it, but the range (e.g. sharediff from 1 to e.g. 100) is up to the pool creator yes? Or is there maybe a consensus/well established rules about it?
Edit: or maybe there is no reason to set the maximum of it?
Quote
If my miner has a sharediff set to 10, I (should) get 10x the credit every time I submit a share. The rules vary by pool.
OK, I get it, but the range (e.g. sharediff from 1 to e.g. 100) is up to the pool creator yes? Or is there maybe a consensus/well established rules about it?
Edit: or maybe there is no reason to set the maximum of it?
65536 is the average number of hashes to be computed in order to find a 1 share at mining difficulty 1 for a bitcoin based coin.
When the pool sets the share-diff to something higher, for example at share diff 10, your miner has to hash 10x more to find that share on average.
So 655360 hashes at share diff 10 and 65536 hashes at share diff 1.
Pools with vardiff or anything similar adjust the share diff to something like 512, because miners with 100's of khashs will have to make more connections to the stratum server at a lower mining difficulty resulting a higher risk of shares being lost. If they send shares at a higher difficulty they will be submitting work less often and have less stales.
Dunno why i'm explaining this or even if it was necessary, i haven't slept so excuse me
Thanks, but now I'm completely lost
Why 65536? Why this *constant*? Doesn't it depend on current network difficulty?
And - why sending sending shares less often results in lower risk of shares being lost?
Network latency and stuff like that cause disruptions in connections now and then.
dunno i'm very tired.
Thanks.
OK, I get it, but the range (e.g. sharediff from 1 to e.g. 100) is up to the pool creator yes? Or is there maybe a consensus/well established rules about it?
Edit: or maybe there is no reason to set the maximum of it?
Quote
If my miner has a sharediff set to 10, I (should) get 10x the credit every time I submit a share. The rules vary by pool.
OK, I get it, but the range (e.g. sharediff from 1 to e.g. 100) is up to the pool creator yes? Or is there maybe a consensus/well established rules about it?
Edit: or maybe there is no reason to set the maximum of it?
65536 is the average number of hashes to be computed in order to find a 1 share at mining difficulty 1 for a bitcoin based coin.
When the pool sets the share-diff to something higher, for example at share diff 10, your miner has to hash 10x more to find that share on average.
So 655360 hashes at share diff 10 and 65536 hashes at share diff 1.
Pools with vardiff or anything similar adjust the share diff to something like 512, because miners with 100's of khashs will have to make more connections to the stratum server at a lower mining difficulty resulting a higher risk of shares being lost. If they send shares at a higher difficulty they will be submitting work less often and have less stales.
Dunno why i'm explaining this or even if it was necessary, i haven't slept so excuse me
Thanks, but now I'm completely lost
Why 65536? Why this *constant*? Doesn't it depend on current network difficulty?
And - why sending sending shares less often results in lower risk of shares being lost?
Thanks.
OK, I get it, but the range (e.g. sharediff from 1 to e.g. 100) is up to the pool creator yes? Or is there maybe a consensus/well established rules about it?
Edit: or maybe there is no reason to set the maximum of it?
Quote
If my miner has a sharediff set to 10, I (should) get 10x the credit every time I submit a share. The rules vary by pool.
OK, I get it, but the range (e.g. sharediff from 1 to e.g. 100) is up to the pool creator yes? Or is there maybe a consensus/well established rules about it?
Edit: or maybe there is no reason to set the maximum of it?
65536 is the average number of hashes to be computed in order to find a 1 share at mining difficulty 1 for a bitcoin based coin.
When the pool sets the share-diff to something higher, for example at share diff 10, your miner has to hash 10x more to find that share on average.
So 655360 hashes at share diff 10 and 65536 hashes at share diff 1.
Pools with vardiff or anything similar adjust the share diff to something like 512, because miners with 100's of khashs will have to make more connections to the stratum server at a lower mining difficulty resulting a higher risk of shares being lost. If they send shares at a higher difficulty they will be submitting work less often and have less stales.
Dunno why i'm explaining this or even if it was necessary, i haven't slept so excuse me
The way the pools work is quite mysterious to me. Slush invented pools, but he's a busy guy. I think I know someone who will know the answer, I'll try to loop him in.
Thanks.
OK, I get it, but the range (e.g. sharediff from 1 to e.g. 100) is up to the pool creator yes? Or is there maybe a consensus/well established rules about it?
Edit: or maybe there is no reason to set the maximum of it?
Quote
If my miner has a sharediff set to 10, I (should) get 10x the credit every time I submit a share. The rules vary by pool.
OK, I get it, but the range (e.g. sharediff from 1 to e.g. 100) is up to the pool creator yes? Or is there maybe a consensus/well established rules about it?
Edit: or maybe there is no reason to set the maximum of it?
1. Why does this even exist? Why not use the target, a pool sends a target
Because inverses and fractions make people happy.
Now diff goes like ~ 1/target.
For long times, network_hashrate/diff ~ constant rather than the product network_harshrate*target. Fraction good, product bad.
...
then why a pool I'm using sends "set_difficulty,240" (stratum), besides on many pools user can set a difficulty between 1 and a few hundred. What is this?
then why a pool I'm using sends "set_difficulty,240" (stratum), besides on many pools user can set a difficulty between 1 and a few hundred. What is this?
Sharediff is different... let a true expert explain better but basically, if you have a super fast miner, you can ask it to only send shares that are twice as good, but only half as often...its a server optimization.
If my miner has a sharediff set to 10, I (should) get 10x the credit every time I submit a share. The rules vary by pool.
Hi,
After reading https://en.bitcoin.it/wiki/Difficulty I understand that difficulty is max diff/current diff.
But I don't understand two things:
1. Why does this even exist? Why not use the target, a pool sends a target (lower than network target) and miners try to find a hash for it. I understand that difficulty is something easier to understand for humans, but why *software* works basing on difficulty?
2. Current difficulty is about 5 006 937 017, then why a pool I'm using sends "set_difficulty,240" (stratum), besides on many pools user can set a difficulty between 1 and a few hundred. What is this?
After reading https://en.bitcoin.it/wiki/Difficulty I understand that difficulty is max diff/current diff.
But I don't understand two things:
1. Why does this even exist? Why not use the target, a pool sends a target (lower than network target) and miners try to find a hash for it. I understand that difficulty is something easier to understand for humans, but why *software* works basing on difficulty?
2. Current difficulty is about 5 006 937 017, then why a pool I'm using sends "set_difficulty,240" (stratum), besides on many pools user can set a difficulty between 1 and a few hundred. What is this?
Jump to: