| proxies |
An off-the-shelf proxy behaves like a dumb forwarder. It does not reduce the number of upstream connections to the pool.
This works but does not give the benefits of a well behaved mining proxy.
A well behaved proxy is one that can let multiple mining instances mine through it, sharing the work space (Nonces) effectively.
Furthermore, with a well behaved proxy you only need to set your upstream address in one place, negating the need to set/change the upstream address on all workers.
XMRIG-Proxy in Nicehash mode does this, as well as the default modes for XMR-Node-Proxy and the new Go-Crypto-Pool proxy based on the old XNP systems.
XMRIG-Proxy outside of nicehash mode does not do this, and is less efficient due to this.
Proxies receive special treatment to handle their higher overall hashrates and help miner owners control their hashrate more effectively.
Here is a list of three proxies:
"A ground-up Go rewrite of the Tari mining-pool stack: "XNP sits between miners and an upstream pool. "An extremely high-performance proxy for the CryptoNote stratum protocol (including Monero and others).
A unified backend service (owning its own Postgres database) plus a shared internal leaf library and three leaf-mode binaries.
It aggregates many downstream miner connections behind one upstream connection by emulating an advanced mining client (XNP-style),
the direct fix for edge connection-scaling problems."
It keeps miner-facing difficulty local, fans out fresh jobs, balances miners across configured pools, and exposes a lightweight HTTP monitor for MoneroOcean-style XMR-family deployments.
It is the share-aggregation edge of the nodejs-pool stack: many miners connect to one proxy, and the proxy presents a smaller set of connections to the upstream pool while preserving algo-switching behavior."
It can efficiently manage over 100K connections on an inexpensive, low-memory virtual machine (with just 1024 MB of RAM).
The proxy significantly reduces the number of connections to the pool, decreasing 100,000 workers down to just 391 on the pool side."
Consider the following:
Install CLI parameters Configuration file http monitor
API Prometheus Other
leaf-proxy Easy yes yes yes yes yes Failover across configured upstream pools.
xnp Skilled yes yes yes yes no Balancing and failover across configured upstream pools.
xmrig-proxy Easy yes yes no yes no
leaf-proxy
./leaf-proxy -upstream-login UPSTREAM_ADDRESS (all defaults to pool-supportxmr.com)
or
./leaf-proxy -config CONFIG.FILE
Use this site often?
There are three ways you can help:
- Point your RX miner to 51.222.84.96:3333 and see your donation progress at secondcreek.ca/ref
- Send XMR to 8BJEAyxCoZaK7sUksfCsAe4KePTM7sAL4M3UjCqd5DcQ5i1H9k6n28kN2QivsNCViQD32WsA3AWCwatLCd4BrHh8DMq4MEK
- Send XTM to 128RyvFUWxpgEkioVTpEepiXTJHwio4scSaBcRh3tw53KduzJAJtZQuw94WwsyEmfHaUBw7o9fXzn72GGKXGZ37szHj