I’ve been running the docker container (with 2 workers) against nanopool for 2 hours now. It’s been running really well.
The container pulls the latest version of the zecproxy from PistoleDev’s repo when it is built. To upgrade when the software is upgraded, you just run the following:
@PistoleDev
Thanks a lot for this great software. I’m using it with nanopool and dstm’s cuda miner at the moment and it works great. When I’ll have more rigs I’ll send you a donation.
Hi @salttrail
Flypool have some issues in difficulty adjustment, so I recommend nanopool.
Zecproxy is recommanded for multiple workers. With 1 rig/worker you can also use zecproxy even if earning will not be really impacted by it.
hi there, @PistoleDev!
I’ve recently tried your soft and it works great, moreover it works with Flypool. The proxy is deployed on ubuntu 16.04 vps machine, and currently 5 rigs are pointed to that machine and it runs for like a week or so. Seems like I get some performance increase, not huge but still like 3-5%. cheers
Hi @zmxrl
Happy to hear that
More rigs you will add, more the earnings will be increased, especially if your proxy is hosted in your local network (raspberry Pi, computer…).
Have an Happy new year guys !
I’m just trying to get it working with the stratum proxy. I have nicehash and claymore both working direct to dwarfpool. Both nicehash and claymore work with the proxy when pointed at nanopool, i just keep getting work rejected when using them pointed at the zec proxy.
I don’t see that it is claymore working/approved.
There site (to me) is not user friendly, spent a good 30 minutes reading their facts and help.
I don’t even see where dwarfpool uses/accepts ssl to use the built in that claymore offers.
To lower your rejection you might need to switch servers and find one with a lower ping
no my point is that when i use the proxy i get rejected work, when i bypass the proxy everything is fine. I’m hoping that by looking at someone’s example working dwarfpool zec proxy config, i can figure out what’s wrong with mine.
Maybe im total nub. But im getting this… tried to get around for some hours now dont tell me its just a easy thing to fix
npm ERR! Linux 4.4.0-97-generic
npm ERR! argv “/usr/bin/nodejs” “/usr/bin/npm” “start”
npm ERR! node v4.2.6
npm ERR! npm v3.5.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! zecproxy@1.0.8 start: node proxy.js
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the zecproxy@1.0.8 start script ‘node proxy.js’.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the zecproxy package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node proxy.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs zecproxy
npm ERR! Or if that isn’t available, you can get their info via:
npm ERR! npm owner ls zecproxy
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/m1/zecproxy/npm-debug.log
Hi @shark1
Yes, you can run the proxy on a rig, just like if you use multiple rigs (all connected to the same proxy, setuped on one of your rigs). But the best way to setup your mining infrastructure (if you are using several rigs) is to put the proxy on a separate machine and connect all your rigs on your proxy.
For the “CPU” usage on the proxy, it’s neglectable.
Have an happy mining
hello pistoledev, i appreciate works such as this. i know i am obliged to backread but is this good for a single rig with 7 gpus cos i read its better if u have multiple rigs? thanks for the time!
