[ANN] Stratum mining protocol - ASIC ready

[slush]

3. Show diff per share submitted in console?

Ok, give me some time.

Check latest git version.

[1714029301]

1714029301

[1714029301]

1714029301

[dlasher]

3. Show diff per share submitted in console?

Check latest git version.

Thank you! Works like a charm!

RE: #2, logging, was hoping to have a log file to pull data from, # of shares per minute, average diff, stuff I can generate easily if I have a logfile, and can then graph. At a minimum, it would be nice to have in syslog so i can redirect it to a central syslog server, on a local1-7.

[slush]

Well, I thought these features are already included in miners. I'm not sure if adding all these features to the proxy is in my time capability :-(

[Keninishna]

Is there a guide for setting up a stratum server? I see the github files but it looks to be just defining the protocol not a actual implementation.

[slush]

Is there a guide for setting up a stratum server? I see the github files but it looks to be just defining the protocol not a actual implementation.

It is working implementation, basically you need to install dependencies (twisted and stratum packages), copy config_sample.py to config.py and run

Code:

twistd -ny launcher_demo.tac -l -

However I don't think too many people tried it yet, so ask me if you'll have any issues. Or even better, join #stratum irc.

[Keninishna]

yup found the twisted file and ran that but I get an error saying cannot import module stratum.

[slush]

It is working implementation, basically you need to install dependencies (twisted and stratum packages), copy config_sample.py to config.py.

run
easy_install stratum
easy_install -U twisted

[dlasher]

Slush:

I ran into an interesting failure state today, and the stratum proxy, I believe, played a roll in the failure. I posted over in the cgminer thread about the cgminer portion, but wanted to post here about the proxy portion.

Scenerio:
- stratum pool proxy is pointed at crashes
- clients behind proxy stay connected to proxy, but get no work
- since connection doesn't 'close' cgminer didn't demote the pool
- all GPU's idling and cold

Shouldn't the proxy, in some way, tell the clients when it's primary upstream connection dies?

[-ck]

Hopefully by now you should be able to cgminer directly to stratum pools more reliably than through the proxy.

[dlasher]

Hopefully by now you should be able to cgminer directly to stratum pools more reliably than through the proxy.

2.8.4 is a dramatic improvement in stratum reliability.. /nod /thankyou

Sadly, none of my individual miners are fast enough (right now) to get over a 1-diff, but together they can get 16-diff when run behind the proxy.

[P_Shep]

Maybe this is a possible future feature of cgminer, being a proxy itself.

[-ck]

Maybe this is a possible future feature of cgminer, being a proxy itself.

Gimme a break 

[jjiimm_64]

Maybe this is a possible future feature of cgminer, being a proxy itself.

Gimme a break 

Then cgminer can get me some coffee too

[eleuthria]

Maybe this is a possible future feature of cgminer, being a proxy itself.

Gimme a break 

Then cgminer can get me some coffee too

Actually, this is a must have feature.  If cgminer is going to support BFL ASICs, which include a "coffee warmer", I think cgminer should interface with my coffee pot to brew my coffee as well.

[P_Shep]

Maybe this is a possible future feature of cgminer, being a proxy itself.

Gimme a break 

Then cgminer can get me some coffee too

Actually, this is a must have feature.  If cgminer is going to support BFL ASICs, which include a "coffee warmer", I think cgminer should interface with my coffee pot to brew my coffee as well.

Stands to reason...

[iCEBREAKER]

Maybe this is a possible future feature of cgminer, being a proxy itself.

Gimme a break 

Then cgminer can get me some coffee too

Actually, this is a must have feature.  If cgminer is going to support BFL ASICs, which include a "coffee warmer", I think cgminer should interface with my coffee pot to brew my coffee as well.

CGMiner must also interface with the grinder and automatically send shares to bitcoincoffee when it runs low on beans.

It should also maintain your ASIC mug warmer at the utmost tastiest temperature for your particular favorite varietal/roast.

*demands BFG send Con more hardware for development*

[Joshwaa]

lolz

[slush]

Hopefully by now you should be able to cgminer directly to stratum pools more reliably than through the proxy.

Can you elaborate more on this? Do you see any bug in proxy?

[-ck]

Hopefully by now you should be able to cgminer directly to stratum pools more reliably than through the proxy.

Can you elaborate more on this? Do you see any bug in proxy?

Don't take it to mean there's a bug. It's simply one less potential point of failure.

[slush]

I ran into an interesting failure state today, and the stratum proxy, I believe, played a roll in the failure. I posted over in the cgminer thread about the cgminer portion, but wanted to post here about the proxy portion.

Shouldn't the proxy, in some way, tell the clients when it's primary upstream connection dies?

Yes, it should. Let me ask some questions:

a) Are you using latest Windows binary?
b) If you're using Linux, are you sure you ran "setup.py install" or "setup.py develop" after last upgrade?
c) Do you see any error/traceback in the proxy during connection outage?

Proxy should propagate all connection failures to all connected miners immediately. It is implemented in method on_disconnect (https://github.com/slush0/stratum-mining-proxy/blob/master/mining_proxy.py) and I don't see any reason why it shouldn't work, except ther was another error.