-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server / Client Idea #537
Comments
Thank you very much for this idea. I'll have a look, as soon as I got the coming release ready. |
That's nice. Will make it much easier to maintain.
…On Tue, May 7, 2019, 4:11 AM RainbowMiner ***@***.***> wrote:
Thank you very much for this idea. I'll have a look, as soon as I got the
coming release ready.
It will improve the client/server application by introducing centralized
config files.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#537 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC6YZSW2Y5PV4DHPNMWGGW3PUFBT5ANCNFSM4HLAZBLQ>
.
|
Could be a support for Monero Ocean pool also implemented as well? |
Implemented. |
Insert your XMR wallet address into pools.config.txt (alt. coins.config.txt and set |
I really like the idea of the server / client model you implemented. Great work.
This may be too much work to handle but now that the server/client model exists, what about integrating proxies, like xmrig-proxy. https://github.com/xmrig/xmrig-proxy
This could be neat but the work to implement it may not be worth the advantage, and I'm not even sure how many cn variants that particular proxy works on. Just throwing it out there.
edit: I think it does support other cn variants but this one that monero ocean supports and is based off xmrig-proxy does support cn variants https://github.com/MoneroOcean/xmr-node-proxy needs to be compiled for windows though.
The text was updated successfully, but these errors were encountered: