bscrk / zecproxy Goto Github PK

bonjour ,j'ai contacté lucas , il ma indiqué comment l'installé sous windows ,

le proxy se lance ,se connecte et trouve du travail.
hors du coté de dtsm lui n'arrive pas à se connecté au proxy

zm --server 192.168.0.10 --user miner_1.rig1 --pass "x" --port 8000

la console se lance , j'ai un delais
et un breff unable to connect et se ferme ,aucun log

( j'ai laissé la config part defaut ,j'ai juste edité l'adresse du wallet part le mien )

une petite video pour monrté le probleme :
https://youtu.be/2tuSaVJtVtg

derriere ça ,je lance la commande avec l'adresse du serveur ( flypool ) et ça demare directe ....

First thank You for great product. i use it with nanopool - increase 10 -12 % hash, but sometimes proxy crashes and go to idle command prompt / not restarted proxy /
I'm totally noob on java , so please help me.
proxy work on main PC , i have 3 miners connected to main PC on same local LAN.
ver 1.0.8

0 info it worked if it ends with ok
1 verbose cli [ 'D:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Users\Fatality\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]prestart: [email protected]
6 info lifecycle [email protected]start: [email protected]
7 verbose lifecycle [email protected]start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]start: PATH: C:\Users\Fatality\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;D:\proxy\node_modules.bin;C:\Users\Fatality\AppData\Roaming\npm;D:\Program Files\nodejs;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.1\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.1\libnvvp;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Program Files\PowerShell\6.0.1;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;D:\Program Files\nodejs;C:\Users\Fatality\AppData\Local\Microsoft\WindowsApps;C:\Users\Fatality\AppData\Roaming\npm;C:\Users\Fatality\AppData\Local\GitHubDesktop\bin
9 verbose lifecycle [email protected]start: CWD: D:\proxy
10 silly lifecycle [email protected]start: Args: [ '/d /s /c', 'node proxy.js' ]
11 silly lifecycle [email protected]start: Returned: code: 1 signal: null
12 info lifecycle [email protected]start: Failed to exec start script
13 verbose stack Error: [email protected] start: node proxy.js
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (C:\Users\Fatality\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:285:16)
13 verbose stack at EventEmitter.emit (events.js:180:13)
13 verbose stack at ChildProcess. (C:\Users\Fatality\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:180:13)
13 verbose stack at maybeClose (internal/child_process.js:936:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
14 verbose pkgid [email protected]
15 verbose cwd D:\proxy
16 verbose Windows_NT 10.0.16299
17 verbose argv "D:\Program Files\nodejs\node.exe" "C:\Users\Fatality\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "start"
18 verbose node v9.8.0
19 verbose npm v5.7.1
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] start: node proxy.js
22 error Exit status 1
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

and go to command prompt idle
Thank You !

Hello.
I permanently get this error. Windows10x64 with nodejs

`2018/01/24 11:49:19 INFO # Work from t1PtCxxxxxxxxxxxxxxxxBt3Lt.ZCLGreen accepted
2018/01/24 11:49:29 INFO # Submit work for t1PtCxxxxxxxxxxxxxxxxBt3Lt.ZCLGreen
2018/01/24 11:49:30 INFO # Work from t1PtCxxxxxxxxxxxxxxxxBt3Lt.ZCLGreen accepted
2018/01/24 11:49:34 INFO # Submit work for t1PtCxxxxxxxxxxxxxxxxBt3Lt.ZCLGreen
2018/01/24 11:49:34 INFO # Work from t1PtCxxxxxxxxxxxxxxxxBt3Lt.ZCLGreen accepted
2018/01/24 11:49:54 ERROR # Network error, Error: read ECONNRESET
2018/01/24 11:49:54 INFO # Connecting to zec-eu1.nanopool.org:6666
2018/01/24 11:49:55 INFO # Connected to pool zec-eu1.nanopool.org:6666
2018/01/24 11:49:55 WARN # Creating workers listner...
2018/01/24 11:49:55 INFO # Subscribing to pool...
events.js:183
throw er; // Unhandled 'error' event
^

Error: listen EADDRINUSE :::8000
at Object._errnoException (util.js:1022:11)
at _exceptionWithHostPort (util.js:1044:20)
at Server.setupListenHandle [as _listen2] (net.js:1351:14)
at listenInCluster (net.js:1392:12)
at Server.listen (net.js:1476:7)
at new MinersController (C:\zecproxy\lib\miners_controller.js:23:8)
at PoolConnector.onConnect (C:\zecproxy\lib\pool_connector.js:32:27)
at Socket.poolSocket.on (C:\zecproxy\lib\pool_connector.js:161:60)
at emitNone (events.js:111:20)
at Socket.emit (events.js:208:7)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: node proxy.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\User\AppData\Roaming\npm-cache_logs\2018-01-24T08_49_55_171Z-debug.log`

log

0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]prestart: [email protected]
6 info lifecycle [email protected]start: [email protected]
7 verbose lifecycle [email protected]start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\zecproxy\node_modules.bin;C:\Users\User\AppData\Roaming\npm;C:\Program Files\nodejs;C:\Python27;C:\Python27\Scripts;C:\Program Files (x86)\Intel\iCLS Client;C:\Program Files\Intel\iCLS Client;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\MSI Afterburner;;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\nodejs;C:\Users\User\AppData\Local\Microsoft\WindowsApps;C:\Users\User\AppData\Roaming\npm
9 verbose lifecycle [email protected]start: CWD: C:\zecproxy
10 silly lifecycle [email protected]start: Args: [ '/d /s /c', 'node proxy.js' ]
11 silly lifecycle [email protected]start: Returned: code: 1 signal: null
12 info lifecycle [email protected]start: Failed to exec start script
13 verbose stack Error: [email protected] start: node proxy.js
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:285:16)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at EventEmitter.emit (events.js:214:7)
13 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:925:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid [email protected]
15 verbose cwd C:\zecproxy
16 verbose Windows_NT 10.0.15063
17 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
18 verbose node v8.9.4
19 verbose npm v5.6.0
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] start: node proxy.js
22 error Exit status 1
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Hi,

Is there a way to change the listening port # to something other than 8000?
Or is it bound / hard-coded that way?

Thanks
Rajesh Thennan

Trying to point the proxy to Slushpool fails.
Used config:

{
"wallet": "XYZ",
"password" : "x",
"port": 8000,
"proxy_name" : "zecproxy",
"enable_worker_id": false,
"pool" : { "host" : "eu.zec.slushpool.com"  , "port" : 4444 },
"pool_failover_enabled": true,
"pool_failover" : [ { "host" : "eu1-zcash.flypool.org"  , "port" : 3333 }],
"restart_delay": 10,
"on_rejected_share": {
                  "strategy" : "restart",
                  "threshold" : 5
                },
"debug" : true
}

Debug output:

[miner@MinerRig1 zecproxy]$ node proxy.js
2018/01/09 23:08:55 WARN # Zcash Stratul proxy version 1.0.7
2018/01/09 23:08:55 WARN # PROXY IS LISTENING ON PORT 8000
2018/01/09 23:08:55 WARN # -----------------------------------------------------------------------
2018/01/09 23:08:55 WARN # Mining Wallet: XYZ
2018/01/09 23:08:55 WARN # Worker ID enabled: false
2018/01/09 23:08:55 WARN # Failover enabled: true
2018/01/09 23:08:55 WARN # -----------------------------------------------------------------------
2018/01/09 23:08:55 WARN # Donation ETH : 0x1212eF39d945aB9A9568Aa5a72c5CBA99Bbe46c1
2018/01/09 23:08:55 WARN # Donation ZEC : t1YAdYcnKR2ozADWPUvmgnDgf86gfsxQEEE
2018/01/09 23:08:55 WARN # -----------------------------------------------------------------------
2018/01/09 23:08:55 INFO # ZEC STRATUM PROXY 1.0.7 STARTING...
2018/01/09 23:08:55 INFO # Connecting to eu.zec.slushpool.com:4444
2018/01/09 23:08:55 INFO # Connected to pool eu.zec.slushpool.com:4444
2018/01/09 23:08:55 WARN # Creating workers listner...
[INFO] Workers controller created
2018/01/09 23:08:55 INFO # Subscribing to pool...
[POOL:OUT] send mining.subscribe: {"id":1,"method":"mining.subscribe","params":["","","Stratum proxy"]}
====================================
[POOL:IN] {"error":[-9,"Cannot call \"mining.subscribe\" - invalid signature",null],"id":1,"result":null}
2018/01/09 23:08:55 ERROR # Proxy failure on state subscribing -9,Cannot call "mining.subscribe" - invalid signature,
====================================
2018/01/09 23:08:55 INFO # Pool closed the connection...
2018/01/09 23:08:55 ERROR # Closing all connections...
[MINERS] Destroy controller
[MINERS] Close workers connections
2018/01/09 23:08:55 ERROR # Waiting 10 seconds before attempting to restart the Stratum Proxy
2018/01/09 23:09:05 WARN # ZEC STRATUM PROXY RESETING...
2018/01/09 23:09:05 INFO # ZEC STRATUM PROXY 1.0.7 STARTING...
2018/01/09 23:09:05 INFO # Connecting to eu.zec.slushpool.com:4444
2018/01/09 23:09:05 INFO # Connected to pool eu.zec.slushpool.com:4444
2018/01/09 23:09:05 WARN # Creating workers listner...
[INFO] Workers controller created
2018/01/09 23:09:05 INFO # Subscribing to pool...
[POOL:OUT] send mining.subscribe: {"id":1,"method":"mining.subscribe","params":["","","Stratum proxy"]}
====================================
[POOL:IN] {"error":[-9,"Cannot call \"mining.subscribe\" - invalid signature",null],"id":1,"result":null}
2018/01/09 23:09:05 ERROR # Proxy failure on state subscribing -9,Cannot call "mining.subscribe" - invalid signature,
====================================
2018/01/09 23:09:05 INFO # Pool closed the connection...
2018/01/09 23:09:05 ERROR # Closing all connections...
[MINERS] Destroy controller
[MINERS] Close workers connections
2018/01/09 23:09:05 ERROR # Waiting 10 seconds before attempting to restart the Stratum Proxy
^C

I just tested this proxy with nicehash to see if it could withstand high load. Long story short: nicehash reports at least a 25% decrease in hashrate. It does not seem to come from rejected shares, but rather the proxy itself is not handling the load or doing something stupid and not forwarding all shares to the pool. Any ideas what is causing this?

Machine running the proxy is powerful enough, it is in Europe and has at most 20ms latency to nicehash. Different pools tested, with low latency as well.

Thanks for this. I haven't really explored NodeJS at all, but I gave this a try on a whim because it was one of only a couple available -- and it seems to work great. I've only used it for ~10 minutes so far, but I'm impressed. I'm already seeing a slight improvement in hashrates, but I'll keep an eye on it over the next few days.

As I'd never used NodeJS before, I looked into compiling it and finally came upon "pkg". I wanted to avoid having to install NodeJS, but I'm glad I did it anyway. I ended up compiled zecproxy into an exe and it works great. I think it would help a lot of people out if you made one available.

I had to do some research, but I made my first NodeJS changes (ever!) under Miner.prototype.onData, to clean up the output from my rigs (which still send their wallet address.workername):

var split = obj.params[0].split(".");
if (split.length > 0) {
	this.name = split[1];
} else {
	this.name = obj.params[0];
}

Also, you confirmed a theory I had about proxifying pool connections to multiple miners -- no need to split up the work amongst them, just let them all work on the same thing and send in the results. I think I'll give this a try on some other crypto in the future.

It's not much, but I sent a small ethereum donation your way! Partly for the program, partly for making me jump into NodeJS, and partly for confirming my theory above. 👍

Hello.
Sometimes I get the following error and zecproxy crashes:

2017/10/25 01:40:03 INFO # Pool closed the connection...
2017/10/25 01:40:03 ERROR # Waiting 10 seconds before attempting to restart the Stratum Proxy
2017/10/25 01:40:07 INFO # Submit work for M1
2017/10/25 01:40:07 ERROR # Network error, Error: This socket has been ended by the other party
2017/10/25 01:40:07 INFO # Connecting to zec-eu2.nanopool.org:6666
2017/10/25 01:40:07 INFO # Connected to pool zec-eu2.nanopool.org:6666
2017/10/25 01:40:07 WARN # Resetting workers...
2017/10/25 01:40:07 INFO # Subscribing to pool...
2017/10/25 01:40:07 INFO # Stratum session id 133b00000000000012ad3f9336937471
2017/10/25 01:40:07 INFO # Authorizing mining wallet t1Qrz2NubDZ2GmsfC2.............................
2017/10/25 01:40:07 INFO # New target : 00028f5c00000000000000000000000000000000000000000000000000000000
2017/10/25 01:40:07 INFO # Mining wallet t1Qrz2NubDZ2GmsfC2............................. authorization granted
2017/10/25 01:40:07 INFO # New work : f0c6102e64d3175a22546a9d5d83a9d338c4477d9bdb16c46a315ebf16884145
2017/10/25 01:40:07 WARN # peer M4 disconnected
2017/10/25 01:40:07 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:07 WARN # peer M4 disconnected
2017/10/25 01:40:07 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:07 WARN # peer M3 disconnected
2017/10/25 01:40:07 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:07 WARN # peer M3 disconnected
2017/10/25 01:40:07 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:07 WARN # peer M3 disconnected
2017/10/25 01:40:07 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:07 WARN # peer M3 disconnected
2017/10/25 01:40:07 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:07 WARN # peer M3 disconnected
2017/10/25 01:40:07 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:07 WARN # peer M3 disconnected
2017/10/25 01:40:07 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:07 WARN # peer M1 disconnected
2017/10/25 01:40:07 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:07 WARN # peer M1 disconnected
2017/10/25 01:40:07 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:07 WARN # peer M1 disconnected
2017/10/25 01:40:07 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:07 WARN # peer M1 disconnected
2017/10/25 01:40:07 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:07 WARN # peer M1 disconnected
2017/10/25 01:40:07 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:07 WARN # peer M1 disconnected
2017/10/25 01:40:07 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:09 WARN # peer M2 disconnected
2017/10/25 01:40:09 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:09 WARN # peer M2 disconnected
2017/10/25 01:40:09 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:09 WARN # peer M2 disconnected
2017/10/25 01:40:09 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:09 WARN # peer M2 disconnected
2017/10/25 01:40:09 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:09 WARN # peer M2 disconnected
2017/10/25 01:40:09 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:09 WARN # peer M2 disconnected
2017/10/25 01:40:09 INFO # 0 peer(s) mining on this proxy
2017/10/25 01:40:13 WARN # ZEC STRATUM PROXY RESTARTING...
2017/10/25 01:40:13 INFO # ZEC STRATUM PROXY STARTING...
2017/10/25 01:40:13 INFO # Connecting to zec-eu1.nanopool.org:6666
2017/10/25 01:40:13 INFO # Connected to pool zec-eu1.nanopool.org:6666
2017/10/25 01:40:13 INFO # Subscribing to pool...
2017/10/25 01:40:13 INFO # Stratum session id db010000000000002d2ed6f2e68c0f4c
2017/10/25 01:40:13 INFO # Authorizing mining wallet t1Qrz2NubDZ2GmsfC2.............................
2017/10/25 01:40:13 INFO # New target : 00028f5c00000000000000000000000000000000000000000000000000000000
2017/10/25 01:40:14 INFO # Mining wallet t1Qrz2NubDZ2GmsfC2............................. authorization granted
2017/10/25 01:40:14 INFO # New work : f0c6102e64d3175a22546a9d5d83a9d338c4477d9bdb16c46a315ebf16884145
/home/tax79/zecproxy/lib/pool_connector.js:85
                this.miners.broadcastToMiners(obj);
                            ^

TypeError: Cannot read property 'broadcastToMiners' of null
    at PoolConnector.onData (/home/tax79/zecproxy/lib/pool_connector.js:85:29)
    at DestroyableTransform.poolSocket.on.pipe.on (/home/tax79/zecproxy/lib/pool_connector.js:158:43)
    at emitOne (events.js:115:13)
    at DestroyableTransform.emit (events.js:210:7)
    at addChunk (/home/tax79/zecproxy/node_modules/ndjson/node_modules/readable-stream/lib/_stream_readable.js:284:12)
    at readableAddChunk (/home/tax79/zecproxy/node_modules/ndjson/node_modules/readable-stream/lib/_stream_readable.js:271:11)
    at DestroyableTransform.Readable.push (/home/tax79/zecproxy/node_modules/ndjson/node_modules/readable-stream/lib/_stream_readable.js:238:10)
    at DestroyableTransform.Transform.push (/home/tax79/zecproxy/node_modules/ndjson/node_modules/readable-stream/lib/_stream_transform.js:146:32)
    at push (/home/tax79/zecproxy/node_modules/ndjson/node_modules/split2/index.js:52:10)
    at DestroyableTransform.transform [as _transform] (/home/tax79/zecproxy/node_modules/ndjson/node_modules/split2/index.js:33:5)

Hi, could you list package requirements and versions (e.g. nodejs)

olSocket = tls.connect(this.current_pool.port, this.current_pool.host, () => {
^
SyntaxError: Unexpected token )
at Module._compile (module.js:439:25)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/root/zecproxy/proxy.js:2:18)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)

on a latest PI installation. looks like i am missing something?

We tested zecproxy with latest Bminer and Miningpoolhub with Auto Exchange and Auto Switching enabled (Equihash only).

The proxy works well but we have noticed a few issues. There is a pretty large occurrence of errors like this

2018/04/04 10:10:55 INFO # Work from rig002 rejected: job not found
2018/04/04 10:06:44 INFO # Work from rig002 rejected: low difficulty share of 1056.3631504974396
2018/04/04 09:52:26 INFO # Work from rig002 rejected: invalid solution

and every 40minutes the proxy restarts itself due to reported issues above.

2018/04/04 10:06:44 INFO # Work from rig002 rejected: low difficulty share of 1056.3631504974396
2018/04/04 10:06:44 ERROR # Too many rejected shares : 5
2018/04/04 10:06:44 WARN #  - rig002 : 5 shares rejected
2018/04/04 10:06:44 ERROR # Closing all connections...
2018/04/04 10:06:44 ERROR # Waiting 10 seconds before attempting to restart the Stratum Proxy
2018/04/04 10:06:44 INFO # Pool closed the connection...

Do you have an idea why this happens? Thanks for your help.

I'm using dstm's ZM miner:
https://bitcointalk.org/index.php?topic=2021765.0

Having quite good success with this pointing at MiningPoolHub's Equihash-hub. However, sometimes it randomly disconnects the miner, causing the miner to crash. Without a watchdog that restarts the miner it leaves the miner idle..
Another issue is that it gives "gpu0 : msg buffer full" after a finite amount of time. Never happened before when mining directly. I can't find anything suspicious in the console..

Any suggestions or ideas..?

Edit:
Also, now with all the different Equihash-coins being released (including Bitcoin Gold), it would be nice to be easily able to redirect hashpower on the fly. I can imagine this being possible if I run 1 proxy for each pool/coin, then add all the different proxies as a failover-pools on the "main" proxy, and then just shut down the proxy I don't want to have hashpower anymore?

Good day I have fixed several issues including a false reporting of rejected shares, no reporting of failed authorizations and have included a config_ for miningpoolhub, and I should probably update the readme with my client/proxy usages.

I would like to push a feature branch to create a pr but am unable to do so, would you like to add me as a contributor?

Thank you,
Troy

Add option e-mail in config
Needed on nanopool

for example nanopool uses self signed cert so the certificate can't be verified with any CA and won't connect over SSL
too many rejected shares and pool disconnects, even with difficulty adjustment.

Please test with SSL pools (important) and work on reducing rejected shares

Looking forward to following

I am getting a "Worker is not authorized" error when using ZECPROXY (1.0.8) with SlushPool (config file pasted below). This seems to occur regardless of whether "enable_worker_id" is set to true or false. Problem seems to be isolated to SlushPool as other pools work. I have also tested against multiple miners with the same results. The only way I can get SlushPool and ZECPROXY to work is when I configure the mining software's wallet or worker to exactly match ZECPROXY "proxy_name" value.

Two Debug files attached: 1) running config file with "enable_worker_id" as true and 2) "enable_worker_id" as false.

{
"wallet": "WALLETXYZ",
"password" : "x",
"port": 8000,
"proxy_name" : "zecproxy",
"enable_worker_id": true,
"pool" : { "host" : "us-east.zec.slushpool.com" , "port" : 4444 },
"pool_failover_enabled": true,
"pool_failover" : [ { "host" : "eu.zec.slushpool.com" , "port" : 4444 } ],
"restart_delay": 10,
"on_rejected_share": {
"strategy" : "restart",
"threshold" : 5
},
"debug" : true
}

zecproxy_debug_workerid_false.txt
zecproxy_debug_workerid_true.txt

There is a offer to implement automatic switching depending on the level of Equihash profitability, for example, data can be taken from whattomine

When using the proxy I average 10.5 KH/s but without it my miners average 11.3 KH/s over a 24 hour period.

Before when i had each rig mine directly to flypool, I could see the worker names in flypool dashboard.

I could know if a rig goes down....

Now, I only see one worker--- because this proxy aggregates multiple rigs to appear as one rig to flypool.

Is there anyway to know which rig is down if one goes down?

work being rejected:

2017/12/08 14:41:40 INFO # Work from strix rejected: u't1g7xxipv7gu4y5rTXei6PTcRoi9DB9gEgD.strix#IP:MAC'

Here is my config.json
{
"wallet": "t1g7xxipv7gu4y5rTXei6PTcRoi9DB9gEgD",
"password" : "x",
"port": 8005,
"proxy_name" : "zecproxy",
"enable_worker_id": true,
"pool" : { "host" : "zec-us1.dwarfpool.com" , "port" : 3333 },
"pool_failover_enabled": true,
"pool_failover" : [ { "host" : "zec-us1.dwarfpool.com" , "port" : 3335, "ssl" : false},
{ "host" : "zec-eu1.dwarfpool.com" , "port" : 3335, "ssl" : false}],
"restart_delay": 10,
"on_rejected_share": {
"strategy" : "restart",
"threshold" : 5
},
"debug" : false
}

I'm not seeing an issue, but i'm sure I missed something simple.

In the instllation instructions, the directoty to choose after git clone, is zecproxy and not zec_stratum

Incorrect:
git clone https://github.com/BScrk/zecproxy.git
cd zec_stratum

Correct:
git clone https://github.com/BScrk/zecproxy.git
cd zecproxy

Additional up to 10-20% increase of earning compared to standard pools
one pc laptop still 10-20% increase of earning?
is for mutli-GPU or for all(one gpu pc laptop)?