Hello, I'd like to be whitelisted, because I have question specific to Slush's pool and I cannot post there as a newbie
... I think I am very well understanding the whole bitcoin theory and I am sure my posts could also help others
My question regarding Slush's pool:
Slush is asking his users to use Stratum interface instead of getwork for miners connecting to his pool. For older miners, Slush has made a Stratum proxy, which should allow older miners to use Stratum interface seamlessly. However, for some reason, this is not working for the miner I am using.
The problem is the target - when I connect to the pool using getwork protocol, the miner reports current target as:
Target = 00000000ffffffffffffffffffffffffffffffffffffffffffffffffffffff
but when I use the Stratum proxy, the miner reports truncated target:
Target = 00000000ffff00000000000000000000000000000000000000000000000000
Theoretically, this should work fine, since hashes, that meet either one of this target are valid, but practically, this does not work for the miner I am using. In the first case, the miner finds hash every few minutes. But in the second case, the miner never finds a hash (I left it running for more than 30 hours). So there certainly is a bug in older miner, but since I cannot use any newer, I wanted to use Stratum proxy.
My question for Slush's Stratum proxy therefore is - why is the pool returning full (untruncated) target in "getwork" response, but Stratum proxy is returning different target (truncated) in "getwork" response. Is this possible to fix, so that my miner does not see any difference, whether connecting to the pool directly, or via the proxy?
thanks...
