github RainbowMiner/RainbowMiner v4.5.3.3
RainbowMiner v4.5.3.3

latest releases: v4.9.1.9, v4.9.1.7, v4.9.1.6...
4 years ago

Update release

Miners

  • update miner CpuminerJayddee to v3.12.3 (cpu)
  • update miner SrbMinerMulti to v0.3.3 (amd,cpu)
  • update miner CpuminerRplant to v4.0.31 (cpu)
  • update miner Nanominer to v1.8.1 (amd,cpu,nvidia)
  • update miner Cryptodredge to v0.23.0 (nvidia)
  • update miner Xmrig to v5.6.0 (amd,cpu,nvidia)
  • add miner 6Miner v0.0.5 (amd,cpu,nvidia)
    • mining HNS/Handshake on 6Block pool

Pools

  • add pool 6Block
    • mining HNS/Handshake
    • needs registration
    • create a Mining Account and enter the account name as wallet in pools.config.txt

Core

  • issue #878: add parameter "ForceStablePrice" to config.txt:
    • if set to "1", all pools, including Nicehash, will use their stable price (slow moving average) to compare. All pools will behave equally, then.
  • update install.sh
    • re-add unintenionally removed -O from wget
  • update MinerAPIs
    • fix return value
  • fix memory checks (issue #879)
  • update Cleanup.ps1
  • linux: invoke ocdaemon after periodic oc profile
  • linux: try to fix overclocking Nvidia (issue #872)
  • linux: add overclocking through "screen", if ocdaemon is not started/used
  • linux: fix end of script
  • linux: move warning from OCDaemon.psm1 to Include.psm1 / Invoke-Exe
  • linux: change "Start-Process screen" to "Invoke-Exe screen" to avoid deadlocks on error.
  • linux: better names for test start-scripts in Bin folders.
  • linux: do not use start-stop-daemon in test scripts in Bin folders.
  • linux: do not write log files in test scripts in Bin folders
  • linux: faster with start-process
  • linux: fix inherent job exit
  • linux: speed up non-ocdaemon scripting
  • linux: keep sh files for overclocking in the miner's Bin folders
  • linux: fix some minor memory leak
  • linux: add WorkerName to screen name to avoid collisions with other RainbowMiner instances

Hints for Networking

Choose one PC to be the Server (it may be a dusty old notebook). No need to let it mine, just let RainbowMiner start in paused mode. Select all other Rigs to act as Clients. All pool API communication will then be managed by the server: no more being blocked by the pools due to excessive use of their API

There is a Network setup build-in the configuration (press [C], then enter [N]) to help with the setup.

If you want it quicker, just run one of the following init scripts for very convenient pre-setup:
InitServer.bat / initserver.sh : make this rig a server
InitClient.bat / initclient.sh : make this rig a client
InitStandalone.bat / initstandalone.sh : make this rig a standalone machine

Of course you may also edit the Config\config.txt directly.

If you change the RunMode of a rig, RainbowMiner needs to be restarted.

Setup as Server

  • one PC takes the role as Server
  • it will act as gateway to the pool APIs for all Clients
  • enable auth: choose an username and a password.
  • the server will be running on the API port
  • optionally provide individual config files for each client

These are the server-fields to fill in the config.txt (or use the initscripts or the build-in config)

  "RunMode": "server",
  "APIport": 4000,
  "APIauth": "1",
  "APIuser": "serverusername",
  "APIpassword": "serverpassword",

Setup as Client

  • all other Rigs shall be clients
  • if you have enable auth at the server: set the username and password.
  • the RainbowMiner running on the server will tell you the machinename, ip address and port
  • use either the machinename or the ip address of the server as servername
  • optionally select to download config files from the server

These are the client-fields to fill in the config.txt (or use the initscripts or the build-in config)

  "RunMode": "client",
  "ServerName": "machinenameofserver",
  "ServerPort": 4000,
  "ServerUser": "serverusername",
  "ServerPassword": "serverpassword",
  "EnableServerConfig": "1",
  "ServerConfigName": "config,coins,pools",

If "EnableServerConfig" is set to "1" (like in the above example), the Client will download the config files defined with the list "ServerConfigName" from the Server. In the example: config.txt, coins.config.txt, pools.config.txt would be downloaded automatically.

Note

As usual: press [U] to update, or exit RainbowMiner and start "Updater.bat" (or let RainbowMiner do the work, if you have set "EnableAutoUpdate" to 1)

If the automatic update fails for any reason, please do a manual update:

  • exit RainbowMiner window
  • if exit fails press image to close the RainbowMiner window
  • now start "Updater.bat" (in RainbowMiner directory)
  • now restart RainbowMiner

If the manual update failed, too, please go the hard way:

  • exit RainbowMiner
  • if exit fails close the RainbowMiner window
  • download the actual release's zip file (name is like RainbowMinerVx.x.x.x.zip)
  • extract the zip file into your RainbowMiner directory, overwriting all files
  • now restart RainbowMiner

Don't miss a new RainbowMiner release

NewReleases is sending notifications on new releases.