so wouldn't it be better (from the miner's point of view) to stay on getwork rather than switching to stratum? NMC is maybe not much value, but probably more than tx fees, isn't it?

Hello Slush,

first of all, thank for your pool, nice work ... although I am mining just for fun (some funny 20 MHash/s  ) and to learn things, I believe that even users like me could be useful for the whole bitcoin and help it grow

And I have a question regarding Stratum proxy, which should allow older miners to use Stratum protocol 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...

LOL

People will never learn a lesson. There always will be enough idiots who think they can make up their fortune by buying special hardware, pills or other magic ...

People, there is no magic, use your brain! 

xorxor, I have a simple answer for all your troubles: if you don't like some pool, DON'T USE IT!

personally I like slush's pool, because I have significantly less hash power than you and I only do some mining for fun and to understand the system a bit more ... and the score based system is sometimes very good for me ... and believe me, none of you people will do mining for long time, bitcoin's futre is something else, not mining 

thanks, I like all the things explained and it is very useful to see it all in the newbies forums

oh thanks, here it is ... when registering, I didn't read all the EULA (or whatever "nobody_reads_it_and_everybody_accepts_it" that was) and then it took me quite long to find these rules

I think I can live with that, but not sure, if that helps someone ...

Hello everybody,

I have long time experience with programming, IT, networks, cryptography, but somehow did not get to know Bitcoin until recently and I really love the idea and hope, that I will be able to help it gain more power and weaken the traditional politicians controlled currencies

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