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

[CheezWiz]

Slush.. or anyone

I am having a difficult time getting my head around the stratum stuff. I am trying to figure out if I will still be able to mine as I have been.
One of my mining locations requires that I mine Via SSH tunnels. So I setup my home router to be an SSH end-point and I run Putty on my miner and open SSH tunnels back to my home router.

So with Phoenix I mine with http://127.0.0.1:8332 which redirects via Putty to http://api.bitcoin.cz:8332 via my home router.
When running CGMiner it first connects via the above, but then gets new info and tries to connect to api-stratum.bitcoin.cz:3333.

I need to get that last connection to go out my SSH tunnel. So I setup a new tunnel http://127.0.0.1:3333 to http://api-stratum.bitcoin.cz:3333 and changed the miner address to http://127.0.0.1:3333 but that does not seem to connect.

Is stratum not connecting via http?

Any ideas how to get what I had before to work with CGMiner and Stratum?

[keystroke]

Is it possible to change the login/email address of an account? I am about to delete a domain I don't really use...

Thanks Slush!

[slush]

Is stratum not connecting via http?

No, it is plain TCP socket.

Any ideas how to get what I had before to work with CGMiner and Stratum?

Make tunnel from localhost:3333 to stratum.bitcoin.cz:3333 (yes, this one, really) and point cgminer to "stratum+tcp://localhost:3333".

[Evan]

Slush,

Is there a reasonable way to figure out BTC per share or BTC per Mhash/s or Khash/s

Just trying to figure out how i want my set up to be with for my 400 Mhash/s stuff :*(

[Epoch]

Is there a reasonable way to figure out BTC per share or BTC per Mhash/s or Khash/s

Try the handy calculator here: https://bitclockers.com/calc

In a no-fee pay-per-share scheme today, you can expect approximately 0.00000727 BTC/share.

For reference, consider this example of a slightly overclocked 5870 GPU:

hashrate: 400Mhps
power: 180W
daily earnings: 0.05849695 BTC ($0.77)
power cost ($0.15/kWH): $0.65
net profit: $0.77 - $0.65 = $0.12

In other words, if you are running a 5870 today you are earning only $0.12/day with it (assuming your electricy cost is $0.15/kWh). And that doesn't include the cost of running the host PC ... if you include that, you are actually losing money by mining. If your electricity is free, your 5870 is bringing in $0.77/day (edit: 0.0585 BTC/day; thanks for catching that, deeplink).

[deeplink]

Is there a reasonable way to figure out BTC per share or BTC per Mhash/s or Khash/s

Try the handy calculator here: https://bitclockers.com/calc

In a no-fee pay-per-share scheme today, you can expect approximately 0.00000727 BTC/share.

For reference, consider this example of a slightly overclocked 5870 GPU:

hashrate: 400Mhps
power: 180W
daily earnings: 0.05849695 BTC ($0.77)
power cost ($0.15/kWH): $0.65
net profit: $0.77 - $0.65 = $0.12

In other words, if you are running a 5870 today you are earning only $0.12/day with it (assuming your electricy cost is $0.15/kWh). And that doesn't include the cost of running the host PC ... if you include that, you are actually losing money by mining. If your electricity is free, your 5870 is bringing in $0.77/day (0.585 BTC/day).

...your 5870 is bringing in $0.77/day (0.0585 BTC/day).

FTFY

[CheezWiz]

Is stratum not connecting via http?

No, it is plain TCP socket.

Any ideas how to get what I had before to work with CGMiner and Stratum?

Make tunnel from localhost:3333 to stratum.bitcoin.cz:3333 (yes, this one, really) and point cgminer to "stratum+tcp://localhost:3333".

Thanks Slush, up and running!

[slush]

Is it possible to change the login/email address of an account? I am about to delete a domain I don't really use...

Just send email request to info@bitcoin.cz from OLD mailbox and I'll do the change manually.

[keystroke]

Is it possible to change the login/email address of an account? I am about to delete a domain I don't really use...

Just send email request to info@bitcoin.cz from OLD mailbox and I'll do the change manually.

Thanks! I sent the email.

[PetrovMichael]

Hi Slush

many thanks for the support and stratum proxy

may be you can modify https://mining.bitcoin.cz/stats/ to show shares per worker per round

for example, last round you gave the data

#   Block found at   Duration   Total shares   Your BTC reward   Block #   Block value   Validity
15104   2012-12-07 17:36:25   0:43:42   1655459   0.04892136   211270   25.28510000    89 confirmations left

modify like below

#   Block found at   Duration   Total shares  Pool Ghash/s   Block #   Block value   Validity
15104   2012-12-07 17:36:25   0:43:42   1655459   2700.550 211270   25.28510000    89 confirmations left

Worker shares Worker Mhash/s Worker BTC reward
32684 5238.4 0.04892136


the question is because i can't find/understand i loosing about 25% shares sent to the stratum proxy ( calculate worker shares sent to stratum proxy and compare to account data Average hashrate in last 10 rounds: 5341 Mhash/s )

many thanks

[slush]

the question is because i can't find/understand i loosing about 25% shares sent to the stratum proxy ( calculate worker shares sent to stratum proxy and compare to account data Average hashrate in last 10 rounds: 5341 Mhash/s )

If you see these shares as accepted, they don't get lost. The 10-round hashrate is just long-term indicator and it needs some time to calibrate.

About your proposed changes - website definitely need some update, unfortunately it's quite difficulty to make right now, because of internal database limitations.

[mdude77]

fyi, I've added support to my pool monitor MPoolMonitor for Slush's pool.  Windows only.

https://bitcointalk.org/index.php?topic=86502.0

M

[slush]

fyi, I've added support to my pool monitor MPoolMonitor for Slush's pool.  Windows only.

Thanks!

[slush]

Today I finally disabled port 8332 on URL mining.bitcoin.cz. Mining is now officially available on api.bitcoin.cz:8332, api2.bitcoin.cz:8332 (getwork) and stratum.bitcoin.cz:3333 (stratum).

URL mining.bitcoin.cz:8332 is deprecated over one and half year, so people had a lot of time to upgrade. If you still have connection issues, please upgrade your miner (old GUIminer had "mining.bitcoin.cz" hardcoded) or update your configs.

[Yuhfhrh]

8 and a half hours since last block solved at slush lol



Edit:
And then 3 blocks in a row to make up for it... blows my mind how that always seems to work out.

[and247]

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

[PetrovMichael]

may be my observation will be useful.

https://mining.bitcoin.cz/accounts/profile/ Average hashrate in last 10 rounds: 5385 Mhash/s.

BUT, observed that when the round is over and a new started -  for about the first 5-10 minutes, shows the performance drop to 4000-4500 Gh/s and later, after the period - shows again about 5200-5400.

when round is long enough

#   Block found at   Duration   Total shares   Your BTC reward          Block #   Block value

15178   2012-12-12 10:07:25   0:55:52   2237452   0.05047476          211918   25.63530000

if round short

15184   2012-12-12 17:11:35   0:08:05   325031   0.04545748          211952   25.05010000

15181   2012-12-12 13:25:39   0:02:45   107333   0.04141353          211934   25.04100000

reward decreased compare to average

i measured shares sent to stratum proxy - IMHO speed stable (by my calculation), so, i'm thinking the question is send/receive shares to the pool

if can make things better, thanks for the advice

[slush]

BUT, observed that when the round is over and a new started -  for about the first 5-10 minutes, shows the performance drop to 4000-4500 Gh/s and later, after the period - shows again about 5200-5400.

"* The calculation is based on the number of shares so far, which may not be accurate for slow workers."

I should add: "it is inaccurate on the beginning of the round also for fast workers".

[slush]

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

Yes, I know there's some miner who has such problem. The easier solution is just to rewrite target in the proxy to 00000000fff...fffff . Then it should work good enough.

Of course the cleanest solution is to fix that miner.

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?

To be honest, that "full" target used by getwork pools was my mistake introduced two years ago, which everybody copy&pasted into their pool implementations. Real diff1 is 00000000ffff00000000000000000000000000000000000000000000000000, which I fixed in Stratum protocol. Fortunately normal getwork miners works with this without a problem, except your one...

[PetrovMichael]

BUT, observed that when the round is over and a new started -  for about the first 5-10 minutes, shows the performance drop to 4000-4500 Gh/s and later, after the period - shows again about 5200-5400.

"* The calculation is based on the number of shares so far, which may not be accurate for slow workers."

I should add: "it is inaccurate on the beginning of the round also for fast workers".

1) if i split my worker to 10 workers - each 500Mh/s, will it make the accepted shares more stable ? 2) what will happened in the April when i will have worker 50 Gh/s ? should i think to split it to 100 workers each 500 Mh/s ?

which speed is optimal for the pool now ?