developer share does nothing

[Makanar]

changing the value "developer share" in config.js does nothing. Changing it from 2 to, 0, 99, and 100 all had no affect on reported hashrate on supportxmr.com. Each time I waited at least 30 minutes for supportxmr.com to update.

{ "pools": [ { "hostname": "pool.supportxmr.com", "port": 7777, "ssl": false, "allowSelfSignedSSL": false, "share": 0, "username": "xxx", "password": "proxy", "keepAlive": true, "coin": "xmr", "default": true } ], "listeningPorts": [ { "port": 7734, "ssl": false, "diff": 5000, "coin": "xmr" }, { "port": 3334, "ssl": false, "diff": 1000, "coin": "xmr" } ], "bindAddress": "0.0.0.0", "developerShare": 100, "daemonAddress": "127.0.0.1:18081", "coinSettings": { "xmr":{ "minDiff": 100, "maxDiff": 300000, "shareTargetTime": 15 }, "aeon":{ "minDiff": 100, "maxDiff": 300000, "shareTargetTime": 15 } } }

[Snipa22]

This works correctly, but it depends on how many miners you have connected as well. It will only slice off full miners, so if you have 100% identical rigs, and a 1% donation, it may not cut off a miner until you reach 100 rigs on the proxy. Make sure you're rebooting between tests/etc.

[Makanar]

shouldn't 100 work though, even with just 1 or 2 miners? One thing to mention is that I have two proxies running from the same folder, I merely added a proxy2.js and a config2.js, and changed proxy2.js to point to config2. I did a pm2 restart proxy2, but I will try a complete reboot.

[bobbieltd]

Developer share is percentage of hash rate to thank Snipa developer. They doesn’t go to your supportxmr. You should put share in pool, “share”: 100 to go to supportxmr and “developer share”: 1. Moreover two variables means different things. One go to your pool, one go to developer.