Quote
[02:36] <@conman> stratum is basically orthogonal to all the hard work I put into network scheduling D:
Topic: [ANN] Stratum mining protocol - ASIC ready - page 30. (Read 146166 times)
I just succesfully tested mining over Tor using Stratum proxy + torify (package torsocks).
# torify ./mining_proxy.py -o pool57wkuu5yuhzb.onion
Console shows some warnings, but it works nicely. Of course direct connection has much lower latency, but for people with concern in anonymity, Tor + Stratum proxy should be a good choice.
Momchil reported that latest poclbm with native Stratum support mining over Tor as well, but you must specify stratum:// directly to let it work properly.
# torify ./mining_proxy.py -o pool57wkuu5yuhzb.onion
Console shows some warnings, but it works nicely. Of course direct connection has much lower latency, but for people with concern in anonymity, Tor + Stratum proxy should be a good choice.
Momchil reported that latest poclbm with native Stratum support mining over Tor as well, but you must specify stratum://
Yes. With the newer version 8.2 the BAMT rigs are now happy campers.
Using 0.8.3 and yes happy campers
Yes. With the newer version 8.2 the BAMT rigs are now happy campers.
Seems like the difficulty implementation of Stratum is causing slight problems with BAMT. Is this due to multiple miners running under the same worker name? Does Stratum know there are more that one worker per name? Just trying to figure some things out.
ckolivas hope all is well now. Glad to hear you will be implementing Stratum. BTW just saw your sig line for the first time. That's some funny shit!
ckolivas hope all is well now. Glad to hear you will be implementing Stratum. BTW just saw your sig line for the first time. That's some funny shit!
Any success? are you using phoenix?
Mining proxy 0.8.2 is out, introducing some workarounds for miner's bugs. I recommend to update.
Well, miners still can work on diff1 shares and proxy will filter out these shares which don't meet difficulty requested by pool server. If there's any bug in the miner regards to difficulty calculations, it should not be triggered by readjustment difficulty by stratum server, because new difficulty won't be propagated into the miner itself.
Ok sorry but you kind of lost me. You say stratum should be giving those workers diff=1, and that's what they are having the problem with? You may have to dumb this down for me a bit.
Hm, I'm thinking that the best solution is to *not* advertise higher difficulty to the miner, but filter our low-diff shares directly in proxy (it is already doing that check). Looks like some miners have serious issues with diff!=1.
I do not see any errors on BAMT or Stratum. Weird I know. From what I can tell if BAMT takes longer that about 7min to find a share it will lock the GPU working on that share. Bamt recovers but then seems to not take work after it does. I am still trying to get more info on the problem. I am running pheonix with phatk2 if this helps.
Joshwaa, which kind of problems? Do you see any errors?
Seems like the difficulty implementation of Stratum is causing slight problems with BAMT. Is this due to multiple miners running under the same worker name? Does Stratum know there are more that one worker per name? Just trying to figure some things out.
ckolivas hope all is well now. Glad to hear you will be implementing Stratum. BTW just saw your sig line for the first time. That's some funny shit!
ckolivas hope all is well now. Glad to hear you will be implementing Stratum. BTW just saw your sig line for the first time. That's some funny shit!
but I will look to implementing native cgminer support when time permits which will hopefully be soon.
Oh Thank god. Dodged a bullet on that one. You are my new best friend.
Surprising that mining has not yet moved away from difficulty-1 mining.
Slush, Eleuthria, glad to see you agreed on and developed a nice protocol for the future. I've been swamped by real life issues for a while now, but I will look to implementing native cgminer support when time permits which will hopefully be soon.
Nice to hear from you again after a hectic two weeks. Sorry to hear that the reason you were away wasn't a positive situation. Whenever you're looking to sit down and play with some code, slush and I are in #stratum, and normally at least one of us is around.
For Stratum testers out there, BTC Guild just introduced dynamic difficulty using the mining.set_difficulty method, with target share rates of between 1 per 3 seconds (faster = diff increased) and 1 per 10 seconds (slower = diff decreased if not already at diff=1). If you have a large farm, you might enjoy hooking up some bandwidth monitoring to your proxy to take a look at how small the network overhead become (make sure you only monitor the non-LAN traffic, since the miners still talk with getwork to the proxy).
Slush, Eleuthria, glad to see you agreed on and developed a nice protocol for the future. I've been swamped by real life issues for a while now, but I will look to implementing native cgminer support when time permits which will hopefully be soon.
Mining proxy executable 0.8.1 for Windows has been released.
Sorry that was incorrect zope and pyOpenSSL were actually not needed. That was for something else.
It makes sense for some individual miners (who run their rigs off cellular modems or something?) might need to reduce bandwidth, but there's no reason they couldn't run a private proxy that does a Stratum-like centralization on their own non-limited connection somewhere.
You mean like I have running right now
.. I don't have dialup, but still saving bandwidth is important so the new mining hardware doesn't DDOS your shiny pool by saturating the pools line.If the GBT thing has been around since February, why aren't all pools and miners already using it?
I am admittedly very new to bitcoin, but not so for software design and programming. That being said, it's just my 2 Satoshis.
Jump to: