Quickstart

We're making everything to make it as easy as possible to start using Midas Dashboard to track status of your mining rigs.

Follow these simple steps:

  1. Get your miner token from the Settings of your profile. You'll need it for your miners to log in. ( Settings )
  2. Download Midas Dashboard Client from the website ( Download )
  3. Copy it to each of your mining rigs, and extract the archive
  4. Create a shortcut for midas_client_startup.exe file. Do NOT give it Administrative rights, this breaks Autostart.
  5. Place it under windows Startup folder: C:\Users\<user name>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
  6. Edit config.yaml file to your liking. It's a plain text file, so you can use notepad to edit it. You can find description of all config parameters below, and inside config file.

That's it! You can start midas_client_startup.exe , and in a few seconds you should see your miner appear in Midas Dashboard! If not, you can take a look at the log, inside CMD window, or in *.log file for hints.

It is also recommended to turn off SmartScreen, as it might interrupt Updater process.

Configuration file

  • MINER_NAME - Friendly name of your miner, that will be displayed in the dashboard.
  • USE_PC_NAME - If set to 1 (or anything BUT 0) it will ignore MINER_NAME and use PC name instead.
  • MINER_API - Midas Client get's it's information from your mining client, it's the most efficient way. Available options:
    • None - this will use OpenHardwareMonitor to get data about your PC. This is temporary, and currently it's a resource heavy process
    • EthDcrMiner64 - Claymore's Miner
    • ewbf - EWBF miner
  • MINER_API_PORT - For some miners port is required.
    • For EthDcrMiner64 use 3333
    • For ewbf use 42000
  • TOKEN - Your server token. To find out your token go to Settings in the Dashboard.
  • GPU_TEMP_WARN: Warning GPU temperature
  • GPU_TEMP_CRIT: Critical GPU temperature
  • GPU_INSTALLED_COUNT: Number of physical GPUs installed in the system. Will be used to check if all GPUs are recognized
  • STARTUP_DELAY: Startup delay in seconds. Client can wait for miners to start up after reboot.

Example:

# Configuration file for Midas Dashboard Client
# This config file is formatted with YAML syntax.

# Display name of this miner. This name will be displayed on your dashboard. Does not have to be unique.
# Note, that you can remove this value from the config file. If it's not here and USE_PC_NAME is set to 0,
# then midas client will ask you to enter a name during it's first start.
MINER_NAME: "Miner"
# If set to 1 (or anything BUT 0) it will ignore MINER_NAME and use PC name instead.
USE_PC_NAME: 0

# Miner program you're using for mining.
# Options are: None, ewbf, EthDcrMiner64
# None will use OHM to get some data
MINER_API: EthDcrMiner64

# For some miners port is required.
# For EthDcrMiner64 use 3333
# For ewbf use 42000
MINER_API_PORT: 3333

# Your server token. To find out your token go to Settings in the Dashboard.
TOKEN: "your_token"

# Warning GPU temperature
GPU_TEMP_WARN: 60

# Critical GPU temperature
GPU_TEMP_CRIT: 75

# Number of physical GPUs installed in the system. Will be used to check if all GPUs are recognized
GPU_INSTALLED_COUNT: 1

# Startup delay in seconds. Client can wait for miners to start up after reboot
STARTUP_DELAY: 0

Miner-specific setup

Some miners have API turned on by default, some not. In case of EthDcrMiner64 you don't need to do anything, midas client will be able to connect to it out of the box. However with EWBF miner you'll need to launch it with --api option enabled. You can refer to EWBF docs on details about how to enable it: https://github.com/nanopool/ewbf-miner

FAQ

Why does client weight about 20MB?

We understand the confusion and security concerns, but there's nothing to be afraid of.

It's written in Python, just as the server, and we even share it's source code on github. You're free to compile your own EXE or even use it as simple Python script. 20MB comes from embedding Python interpreted into EXE file. We're thinking about writing a smaller client, but on current stages Python is much more flexible.

https://github.com/Midash/midash_client_py/tree/master