[4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool

[BitMinerN8]

Mining proxy 1.1.1 has been released (including EXE for Windows users). Update is higly recommended for Windows users, there's really lot of changes since last Windows release (0.9.0).

https://github.com/slush0/stratum-mining-proxy/downloads

Thanks! Testing now on Win & Linux. 

[1685410718]

1685410718

[1685410718]

1685410718

[1685410718]

1685410718

[1685410718]

1685410718

[1685410718]

1685410718

[Aahzman]

Ok, downloaded, running. whuz da changes at?

[slush]

Ok, downloaded, running. whuz da changes at?

Changelog is here: https://github.com/slush0/stratum-mining-proxy/commits/master

The biggest difference between 0.9.0 (used by majority of people now) and latest 1.1.1 is proxying of Stratum protocol itself, instead of proxying only getwork->stratum. Thanks to this, you can connect your exahash/s mining operation to the pool with single connection, transfering up to 20kB per minute.

Latest version also fixes many smaller bugs in connection management; the most important is bugfix in client.reconnect() which allow miner to reconnect to another pool backend if pool need to do some maintenance on current one.

[Aahzman]

cool stuff. ain't a networking guy so i have only a basic understanding of proxies. 

So it appears to be only the Summary tab in GUIMiner that likes to freeze...it's still hashing, but doesn't show the second-to-second changes in hashrate. Now i just leave it on the Default tab. :-)

It's workin, that's all that matters. HOpefully, it stays working smoothly all weekend while i'm up at the fiancee's for a couple days.

[keystroke]

Ok, downloaded, running. whuz da changes at?

Changelog is here: https://github.com/slush0/stratum-mining-proxy/commits/master

The biggest difference between 0.9.0 (used by majority of people now) and latest 1.1.1 is proxying of Stratum protocol itself, instead of proxying only getwork->stratum. Thanks to this, you can connect your exahash/s mining operation to the pool with single connection, transfering up to 20kB per minute.

Latest version also fixes many smaller bugs in connection management; the most important is bugfix in client.reconnect() which allow miner to reconnect to another pool backend if pool need to do some maintenance on current one.

Great, just upgraded my 2.9Ghash to the latest proxy. Looks good. Next stop, ASIC.

[slush]

People concerned about Stratum protocol security (versus GBT), please read https://bitcointalk.org/index.php?topic=108533.msg1287719#msg1287719

[TheMan]

I mine at 360 M/hash using two workers for my account each with Radeon HD 6850. I get about 0.1 +/- 0.02 BTC per day with about 0.008 +/- 0.002 reward per round.
Just checking if that's normal, or I can optimize better?

P.S. I don't pool hop if you are wondering, sometimes I lose my second worker, at which my reward drops to 0.005 to 0.003 per round. I remember a month ago I was able to get 0.007 per round just by myself and its not like the system reward dropped so I was wondering... since all that's changed is the overall hash rate of the pool, from 1800 G/hash to about 2000 G/hash.

EDIT
I use stratum with OpenCl miners on GUIminer version 2011-05-01 since I felt that this one worked the best.

[slush]

Just checking if that's normal, or I can optimize better?

Comparing daily income or even round reward isn't good enough, because there's many variables involved, like short-time pool luck, total pool hashrate etc. You should focus to your hashrate; more is better.

I use stratum with OpenCl miners on GUIminer version 2011-05-01 since I felt that this one worked the best.

Please use latest GUIminer, not that 2011 version. There are known issues in this version.

[TheMan]

Please use latest GUIminer, not that 2011 version. There are known issues in this version.

The latest one doesn't let me connect to stratum...

[digital]

Please use latest GUIminer, not that 2011 version. There are known issues in this version.

The latest one doesn't let me connect to stratum...

It does.  Not sure where your going wrong cause I'm using the latest version with the same setup as you.

You need to select solo in the drop down box, then put just localhost for the host, and all the other information should stay the same.

[TheMan]

It does.  Not sure where your going wrong cause I'm using the latest version with the same setup as you.

You need to select solo in the drop down box, then put just localhost for the host, and all the other information should stay the same.

In the old one, I had "other" selected and it worked, so yeah, that was the problem. Anyhow, my hash rate is lower on the newer version. Have about 180 M/hash to 190, while on the new miner with the same setting I get 150 M/hash...

[digital]

It does.  Not sure where your going wrong cause I'm using the latest version with the same setup as you.

You need to select solo in the drop down box, then put just localhost for the host, and all the other information should stay the same.

In the old one, I had "other" selected and it worked, so yeah, that was the problem. Anyhow, my hash rate is lower on the newer version. Have about 180 M/hash to 190, while on the new miner with the same setting I get 150 M/hash...

using the same flags?  I've changed versions of guiminer with opencl probably 4 or 5 different times and have never seen a difference that big in hash rate...

[TheMan]

using the same flags?

I keep my flags blank (use no flags) for both of the versions, so i guess that counts as a yes...

[digital]

using the same flags?

I keep my flags blank (use no flags) for both of the versions, so i guess that counts as a yes...

Try using:
-v -w256

I've got a couple 6850's and that's what I use.  It might get you back up to 180.  Almost all my cards are 6000 series, and I always use -v, and always -w with either 128 or 256, you can tweak that number to find which one works best (64, 128, 256, etc).  And you can also try adding -f1, I use it on about half my cards, sometimes it makes a difference, sometimes it doesn't...

[TheMan]

using the same flags?

I keep my flags blank (use no flags) for both of the versions, so i guess that counts as a yes...

Try using:
-v -w256

I've got a couple 6850's and that's what I use.  It might get you back up to 180.  Almost all my cards are 6000 series, and I always use -v, and always -w with either 128 or 256, you can tweak that number to find which one works best (64, 128, 256, etc).  And you can also try adding -f1, I use it on about half my cards, sometimes it makes a difference, sometimes it doesn't...

Thank man, I'll try it out!

[TheMan]

Woa! kicked me up to 200 M/hash, thanks a lot digital!

[digital]

lol, my pleasure.

And for future reference, if you ever get new or different cards, you can always go to the below url to find out what flags to use.

https://en.bitcoin.it/wiki/Mining_hardware_comparison

[Aahzman]

sorry if this has been answered somewhere else, but why does the pool software wait the full 100 confirmations before issuing rewards? Just curious...

Also, reading this last page...been mucking about with my -w setting for my MIS HD6770....tried a whole range of em...64, 128, 192, 256, 320, 384, etc all the way up to 2048....no noticeable jump or crash in hashrate.......do i need to stop my miner, change it, then restart to see any difference?

[slush]

sorry if this has been answered somewhere else, but why does the pool software wait the full 100 confirmations before issuing rewards? Just curious...

This is basic rule implemented in Bitcoin protocol itself; miner can manipulate with freshly mined coins after generated block is already 100 other blocks deep in blockchain. Btw official Satoshi client requires 120 confirmations.

[digital]

Also, reading this last page...been mucking about with my -w setting for my MIS HD6770....tried a whole range of em...64, 128, 192, 256, 320, 384, etc all the way up to 2048....no noticeable jump or crash in hashrate.......do i need to stop my miner, change it, then restart to see any difference?

I'm not totally sure if you have to stop and restart the miner after making a change, but I normally do as a rule of thumb.   After I change anything on my miner I'll hit stop, then immediately hit start, then save (of course provided you like the settings).