search

MoneroOcean / xmr-node-proxy

Cryptonote/Forknote/Cryptonight/Light/Heavy coin proxy for nodejs-pool
77 stars 60 forks source link

multi-pool with different algo miner type #77

Open MrCook1es opened 6 years ago

MrCook1es commented 6 years ago

Hi, i'm using XNP fork from MO and works great. The forks has no problem, and after the update all works fine.

The question is: can I have in the config.json file 2 pool, the first pool with "cryptonight/2", the second pool with "cryptonight/1". And than have 10 updated CN2 miner on the first pool, and other 10 old miner CN1 connected on the second pool? (setting different port is not a problem)

MrCook1es commented 6 years ago

something like:

POOLS pool1 cryptonightv7.eu.nicehash.com:3363 -> "cryptonight/1" pool2 supportxmr.com:5555 -> "cryptonight/2"

LISTENING PORTS - miner side on pool1 i have old miner with cn/1 on port 8080 on pool2 i have updated miner with cn/2 on port 3333

is it possible? How can i setup the config file correctly?

MoneroOcean commented 6 years ago

No it is not possible at this moment. Proxy can not divide miners based on their algo support between pools.

MrCook1es commented 6 years ago

Thanks for the reply

sothcott commented 6 years ago

I'd like to use two pools but based on port number so two different groups of rigs can mine to different wallets. I suppose I need two instances of xmr-node-proxy if I can figure out how to do that.

bobbieltd commented 6 years ago

Not tested, you can tweak by copying xmr.js to xmr2.js and then you can use coin : “xmr2” for the second group of workers as you wish.

sothcott commented 6 years ago

I've done it using docker. First one is in PM2 second one in docker with different config.json docker create -p 3334:3333 -p 8181:8080 -p 8444:8443 --name xnp1 xmr-node-proxy

a bit rough and ready but working. I expect docker would allow multiple xmr-node-proxy instances all with different config files but I'm not that skilled yet.