How to set up backup pools

Some mining clients allow you to define backup pools so in case the main pool isn't working or is having issues, you will mine to a second pool.

In this article, we will show you how to do that on most popular Ethash mining clients. You can also check the official documentation of your mining client to find the detailed instructions.

  • (POOL:ETH)⁣ is a tag in which we save initial pool
  • (POOL:ETH-BACKUP)⁣ is a tag in which we save backup pool
  • (WALLET:ETH)⁣ is a tag in which we save wallet address
  • (WALLET:ETH-BACKUP)⁣ is a tag in which we save wallet address that will be used alongisde backup pool

Phoenix miner

Phoenix miner has a special parameter -pool2 where you can define the second failover pool and -wal2 where you can define wallet address that will be used with the failover pool. If -wal2 is not defined, a wallet defined in -wal will be used with the failover pool.

-worker (WORKER)⁣⁣ -pool (POOL:ETH)⁣ -pool2 (POOL:ETH-BACKUP)⁣ -wal (WALLET:ETH)⁣.(WORKER) -wal2 (WALLET:ETH-BACKUP)⁣.(WORKER) -pass x -eres 0 -log 0 -gbase 0 -proto (AUTO)⁣

T-Rex

In the configuration we are using for TREX mining client (a JSON format), you can define a list of pools directly from your worker's config and they will be used in defined order in case they fail.

{
 "pools": [
  {
   "user": "(WALLET:ETH)⁣",
   "worker": "(WORKER)⁣⁣",
   "url": "(POOL:ETH)⁣",
   "pass": "x"
  },
  {
   "user": "(WALLET:ETH-BACKUP)⁣",
   "worker": "(WORKER)⁣⁣",
   "url": "(POOL:ETH-BACKUP)⁣",
   "pass": "x"
  }
 ],
 "no-nvml": true,
 "api-bind-http": "127.0.0.1:4068",
 "json-response": true,
 "pci-indexing":true,
 "retries": 3,
 "retry-pause": 5,
 "timeout": 500,
 "no-watchdog":true,
 "algo": "ethash",

 "exit-on-cuda-error": true,
 "exit-on-connection-lost": false
}

For CLI version of T-Rex configuration you can just define pool, user, and password parameter side by side like shown in the following syntax.

--algo ethash --url (POOL:ETH)⁣⁣⁣⁣⁣⁣ --user (WALLET:ETH)⁣⁣⁣⁣⁣⁣⁣.(WORKER)⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣ --pass x --url (POOL:ETH-BACKUP)⁣⁣⁣⁣⁣⁣ --user (WALLET:ETH-BACKUP)⁣⁣⁣⁣.(WORKER) --pass x --worker (WORKER)⁣

lolMiner

In the configuration we are using for lolMine mining client (a JSON format), you can define a list of pools directly from your worker's config and they will be used in defined order in case they fail.

{ "MINERSTAT" : { "DEVICES" : "AUTO", "APIPORT" : 3333, "ALGO" : "ETHASH", "POOLS" : [ {"POOL" : "(POOL:ETH)⁣", "PORT" : "(AUTO)⁣", "USER" : "(WALLET:ETH)⁣.(WORKER)⁣", "PASS" : "x"}, {"POOL" : "(POOL:ETH-BACKUP)⁣", "PORT" : "(AUTO)⁣", "USER" : "(WALLET:ETH-BACKUP)⁣.(WORKER)⁣", "PASS" : "x"} ] } }

TeamRedMiner

TeamRedMiner allows you to define multiple -o parameters where you can define failover pools. You also need to specify the username and password for each pool. For simple fail-over use you can duplicate the -u and -p entries:

--algo ethash -o (POOL:ETH)⁣ -u (WALLET:ETH)⁣.(WORKER)⁣ -p x -o (POOL:ETH-BACKUP)⁣ -u (WALLET:ETH)⁣.(WORKER)⁣ -p x --eth_dag_slowdown=9 --watchdog_script=/home/minerstat/minerstat-os/bin/reboot.sh --eth_no_ramp_up

Gminer

Gminer allows you to define multiple -server and -user parameters where you can define failover pools and user/wallet credentials that go with it.

--pass x --algo ethash --server (POOL:ETH)⁣ --user (WALLET:ETH)⁣.(WORKER)⁣ --server (POOL:ETH-BACKUP)⁣ --user (WALLET:ETH-BACKUP)⁣.(WORKER)⁣ --port (AUTO)⁣ --ssl 0

Stratu.ms

You can also use our Stratu.ms service and generate your mask stratum, where you can define up to 2 backup pools.

Improve your mining operation with minerstat

It's easy and free to get started

Sign up now