[1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff]

[Edgge]

yeah me too doc been having a blast at your place

[1686314023]

1686314023

[1686314023]

1686314023

[DrHaribo]

Thanks for the support. It's very good to see the pool growing again.

You maybe should say on the front page that the pool is now protected against DDoS by black lotus. That might make many people come back here. Just sayin'...

Good idea. Added, along with a link to the Mint Race thread.

[philipma1957]

Thanks for the support. It's very good to see the pool growing again.

You maybe should say on the front page that the pool is now protected against DDoS by black lotus. That might make many people come back here. Just sayin'...

Good idea. Added, along with a link to the Mint Race thread.

nice to read the black lotus is on board.

[DrHaribo]

After a slow start farfie gets the first block. It remains to be seen whether this will keep him in the top 10. With almost a week left of the race, anything could happen.

[Edgge]

thinking about giving up I have no hash rate and am not doing well

[oroboras]

Luck seems to be in the gutter at the moment, but it's sure to pick up eventually
It can hardly get worse, lol!

[Epoch]

In the long run, statistically, BitMinter is one of the best pools (if not *the* best) to mine at. But for those with an aversion to variance, one way to reduce variance is to distribute your workers among multiple pools. I don't mean failover; I mean set one worker to Pool A; another to Pool B; another to Pool C. Etcetera. In that way, you will reduce your variance.

[derekleong75]

5+Th...
Welcome back boys!
Here's some champagne for the big hashers.

[Paulizei]

5+Th...
Welcome back boys!
Here's some champagne for the big hashers.

The reason is that slush's pool is down, I guess

[Paulizei]

What is this? A block with 0 work?

243093    2013-06-24 12:16    0m    0    19,339,258    0.0%    0.000    BTC    hellerstern66    119 left

[desired_username]

5+Th...
Welcome back boys!
Here's some champagne for the big hashers.

Slush is down, so I guess that's the spike in bitminter hashrate. At least that's why I'm here. As soon as slush fixes the problem I'll go back though.

The reason is, my blades report 12.5-13GHS at slush and it goes down to 11-11.5Ghs when mining on bitminter :S

[Paulizei]

The reason is, my blades report 12.5-13GHS at slush and it goes down to 11-11.5Ghs when mining on bitminter :S

Stats here at the mint are more like a guess - at least not accurate.
When you completed at least one shift, the "your ghps" value on the live stats page should show a better value.

[desired_username]

The reason is, my blades report 12.5-13GHS at slush and it goes down to 11-11.5Ghs when mining on bitminter :S

Stats here at the mint are more like a guess - at least not accurate.
When you completed at least one shift, the "your ghps" value on the live stats page should show a better value.

I'm getting these values from the management interface of the blades not the pool.

[Paulizei]

I'm getting these values from the management interface of the blades not the pool.

Oh ok. That's something different then. And something I can't explain. Sorry

[grosskate]

The reason is, my blades report 12.5-13GHS at slush and it goes down to 11-11.5Ghs when mining on bitminter :S

Stats here at the mint are more like a guess - at least not accurate.
When you completed at least one shift, the "your ghps" value on the live stats page should show a better value.

I couldn t even know if my miners were working correctly at slush on its front end. Most of the time i was seeing them not hashing at all or only some of them sometimes even though they were on and getting shares. I contacted slush about it but never got an answer. Doc haribo s always replied to any of my emails sent to him. My stats are way better here at bitminter than at slush. Moreover now we have black lotus protection from DDoS attack

Well it s a matter of point of view, habits and trust regarding the pool  i guess... :-)

[DrHaribo]

The reason is, my blades report 12.5-13GHS at slush and it goes down to 11-11.5Ghs when mining on bitminter :S

If you are connecting the blade directly to the pool with the getwork protocol, try instead to set up a stratum proxy and connect through that. In that case the hashrate will be exactly the same.

The stratum proxy will be generating new work locally and the blade hashing it, so the blade should be running full speed all the time. If the hashrate is different then you probably didn't measure it long enough to even out inaccuracies.

[Paulizei]

Pool is down!

[DrHaribo]

Pool is down!

Just restarting the mining service.. it's a bit slow on the restart though - I will work to improve that.

[not.you]

What is this? A block with 0 work?

243093    2013-06-24 12:16    0m    0    19,339,258    0.0%    0.000    BTC    hellerstern66    119 left

Wondering on that one myself.

[Paulizei]

Pool is down!

Just restarting the mining service.. it's a bit slow on the restart though - I will work to improve that.

Ah ok. Thanks for your quick reply, Doc!