home · our customers · news · S9 · T9+ · documentation · support/contact · changelog · about · pool · psu · restore ssh · fix hashboards
asicseer logo
ASIC management, monitoring, and optimization system.

ASICseer is running on 41,370 ASICs (46.9 megawatts).

download ASICseer now: usflag ruflag

Table of Contents

Quick Start Guide (with ConfigMaker)

ASICseer is separated into read-only and read-write. Your Panel is read-only and your Remote Config File is read-write.

  1. Go to ASICseer Downloads.
  2. Upon loading the page, a Remote Config File will automatically be generated and hosted on ConfigMaker.com for you.
  3. Save/Bookmark your SECRET EDITOR LINK, you will need it to manage all of your ASICs.
  4. Set your custompanel (useful for multiple locations to report to the same Panel).
  5. Follow the instructions under "Simple and Easy" installation and wait for the installation to complete.
  6. After the installation finishes, visit the "Miner Configuration" page on your ASIC.
  7. Make changes to your ConfigMaker Remote Config File to manage your ASICs.

You can use the "Powerful and Advanced" installation to quickly install ASICseer on multiple units via SSH.

Setting up your own Remote Config File

If you don't want ConfigMaker to host your Remote Config File, you can host it yourself on a world-reachable remote server, vps, or shared hosting account that you control.

  1. Copy https://asicseer.com/config.txt and host it yourself on a world-reachable remote server, vps, or shared hosting account that you control.
  2. Get the link to your Remote Config File like http://your-server.com/config.txt
    NOTE: The link http://your-server.com/config.txt is an example. You must use your own link.
  3. Set your custompanel (optional, but recommended), edit the Remote Config File to suit your preferences.
  4. Make changes to your Remote Config File to manage your ASICs. See Writing your Config for documentation.
  5. Paste the link to your Remote Config File into the "Remote Config File" field on the Downloads page and click "Regenerate Downloads."

Setting up a Server for your Remote Config File

If you don't have a remote server and don't want to use ConfigMaker, you can create a remote server with DigitalOcean.

  1. Go to DigitalOcean (follow this link to get $50 credit), create an account, then click "Create -> Droplet."
  2. Click on "Marketplace" and select "LEMP on 18.04" software stack.
  3. Scroll down, click the left arrow, select "$5/month" droplet (not $40/month), your closest region, "one-time password", and click "Create."
  4. After the droplet is created, follow the SSH guide to SSH to your DigitalOcean droplet.
  5. Descend into the world-readable html directory with cd /var/www/html
  6. Copy the sample Remote Config File to your DigitalOcean Droplet with wget https://asicseer.com/config.txt
  7. Make changes to your Remote Config File on your DigitalOcean droplet with nano /var/www/html/config.txt
  8. The link to your Remote Config File is now http://digital.ocean.ip.address/config.txt
  9. Paste the link to your Remote Config File into the "Remote Config File" field on the Downloads page and click "Regenerate Downloads."

Using the multi-ASIC installer on Windows 10

Preparatory Instructions

  1. Update Windows 10 to at least Version 10.0.18362 (Build 18362).
  2. Download and Install Nmap (do not change the installation path during installation).
  3. Download and Install Ubuntu 18.04 from the Microsoft Store.

Ubuntu Windows Subsystem for Linux (WSL) Instructions

  1. When Ubuntu prompts Enter new UNIX username: use asicseer for both the username and password settings.
  2. Once the username and password is set, sudo su to become the root user.
  3. When prompted for your password, enter asicseer
  4. Run the below line to install the required packages:
    apt-get update; apt-get -fy install sshpass; rm -f /usr/bin/nmap; ln -s "/mnt/c/Program Files (x86)/Nmap/nmap.exe" /usr/bin/nmap

You have now installed all required packages and have prepared a Linux environment. Proceed with "Using the multi-ASIC installer on Linux".

Using the multi-ASIC installer on Linux

  1. Add your vlans into your Remote Config File (example). Each vlan must be specified like: (last octet is a range).
  2. Add your ASIC root password (usually "admin") into your Remote Config File as shown in the example.
  3. sudo su to become root. You must actually be root to run this installer.
  4. Install nmap sshpass awk sha256sum curl if your linux box doesn't have them installed, examples:
    • ubuntu, debian: apt-get -fy install nmap sshpass
    • ethos: apt-get-ubuntu -fy install nmap sshpass
    • fedora, centos: yum -y install nmap sshpass
    • windows wsl: apt-get update; apt-get -fy install sshpass; rm -f /usr/bin/nmap; ln -s "/mnt/c/Program Files (x86)/Nmap/nmap.exe" /usr/bin/nmap
  5. Follow the Quick Start Guide to generate your installer script.
  6. Copy/paste the line under "MULTI-ASIC INSTALLER" into your linux box and press ENTER.
  7. Wait for the installation process to start.
  8. The installer output will fill your screen. Once there is no more output (you can check by pressing ENTER), the installation is finished.

Writing your Config

Your entire farm can be controlled with a single Remote Config File. Your Remote Config File is downloaded and applied to your ASIC every 10 minutes, so any changes can take up to 10 minutes to take effect.

For faster responsiveness (every 2 minutes instead of 10 minutes), host your own Remote Config and add RESPONSIVE to its URL (example: http://your-server.com/configRESPONSIVE.txt)

See https://asicseer.com/config.txt for an example Remote Config File. Everything with a hashtag/poundsign is a comment, and is ignored by all scripts. All settings, except for usernames, wallets, and passwords, are always lowercase.

Formatting Overview

The format for editing your Remote Config File is asicid setting value where:

Use global for the asicid to apply a setting to all ASICs on which you have installed the same Remote Config File.

Panel Settings

Pool Settings

Pool Settings for the Failover Pools

To prevent pool-related downtime, you must have poolname1, poolname2, and poolname3 defined to at least two different pool domains/companies (see ASICseer recommendation).

Power Settings

Advanced Settings

LED Settings


global blinkgreen hashrate
global blinkred idle

hashrate blinks faster as hashrate increases, solid if tuning
idle turns on light if ASIC is not mining
fan turns on light if a fan is not detected and blinks if a fan is degrading
rapid blinks rapidly
solid solid light
off no light
morse code 
sos blinks sos in morse code
worker blinks the worker name in morse code
ip blinks the ip in morse code
panel blinks the panel name in morse code
location blinks the location in morse code

Temperature Settings

ASIC Troubleshooting Settings

The below settings take an incrementing value. It is recommended to use the unix timestamp for these settings: 1576109870


group searches the beginning of your location for a string and applies your setting to any ASIC location that has a match.

The location must start with the string to match. The below example will reboot ASICs with a location starting with rowc, and will stop mining on ASICs with a location that has rowd in it.

You must have locations defined for grouping to work.

group=rowc reboot 1
group=rowd allowed no

Customizing your Worker Name / Location

You can use one Remote Config File for all ASICs. Specifying multiple workers does not require separate Remote Config Files.

To switch your worker name and assign a location, set asicid location newname

Assigning Worker Names / Locations with the IP Report Button

If you use hostnames to manage your worker names and ASIC locations, ASICseer will use them to set Worker Names / Locations during installation. If you have a big farm and don't know where any of your ASICs are located, you can order them with the IP Report button located on your ASICs.

NOTE: It is important to do the below steps when your Internet is stable, and your ASICs are online and reporting.

  1. After installing ASICseer, go to your Panel. Then, physically go to your first Rack ("Rack A") and decide on an order for them.
  2. Press and hold the IP Report button for 5 seconds on each "Rack A" ASIC in order, one by one (wait at least 3 seconds between press-holds).
  3. Wait at least 3 minutes.
  4. Your Panel will show a number in the "ipr" column (seconds ago that the IP report button was pressed).
  5. Select "assign workers" from the dropdown menu and click the "submit" button.
  6. Set your worker names like: a1,a2,a3...
  7. Continue this process for all rows/racks. If you press the IP report button on all ASICs in your preferred order, they will be ordered correctly.

Assigning Worker Names / Locations with REGEX

If you use static IPs for your ASICs, you can use regex to assign IP octets for your worker name and location.

  1. After installing ASICseer, go to your Panel.
  2. Select "config template" from the dropdown menu and click the "submit" button.
  3. Copy and Paste the config template into the "TEST STRING" field of regex101.com's regex editor.
  4. Copy and Paste the resulting "SUBSTITUTION" result into your Remote Config File and save it.

After 10 minutes, all your ASICs will have downloaded and applied the new settings, the new locations will be set on your Panel, and the new worker names will be sent to your pool.

Remotely Rebooting ASICs

If your ASICs are reachable (i.e. they don't have a ❌ icon), you can reboot them remotely using your Remote Config File.

  1. Go to your Panel.
  2. Select the checkboxes to the left of the conditions affecting your ASICs, select "reboot manager" and click the submit button.
  3. Your Panel will generate settings for your Remote Config File to reboot your affected ASICs
  4. Copy-paste the entire output into your Remote Config File.
  5. Within 10 minutes, all affected ASICs will reboot.

Reducing Facility Overheats

Due to environmental conditions (fan health, physical location, airflow, etc) not all ASICs can operate at the same maxwatts setting. You can maximize hashrate by tuning your entire facility to each ASIC's individual highest possible maxwatts with the below guide:

global maxwatts 1480
global maxtemp 90 6
global throttle 80


  1. Start mining/tuning at 1480 watts.
  2. If any hashboard reaches 90C, trigger an overheat and stop mining.
  3. Restart mining automatically after 6 hours passes.
  4. If mining is restarted after an overheat, throttle maxwatts by 80 watts (i.e. 1400, then 1320, etc).
    NOTE: The minimum and maximum settings for throttle are 25-200 watts.
  5. Each ASIC will automatically tune to its highest possible maxwatts setting, with as much granularity as you prefer.

Temperature Legend

To restore throttled ASICs back to their original maxwatts setting, add this line to your Remote Config File:
global uncork 1576109870 (use the asicid instead of global).

ASICs throttling/overheating due to unaddressed environmental conditions will throttle again even after uncork is run.

You can use LED settings to find ASICs with temperature problems, and diagnose them for physical problems or environmental conditions. You can also physically swap ASICs in your farm.

ASICs that are too cold cannot maintain their hashrates. Decrease or block facility airflow and exhaust in sections of your facility that have an abnormal amount of cold ASICs.

Managing Temperature

If any hashboard temperature exceeds maxtemp, mining will turn off for the amount of hours defined (default 6)

Follow the below steps to reduce the chances of your ASICs overheating:

Setting a Custom Panel

ASICseer assigns a 6-character Panel based on a hash of your external IP. This way, all ASICs on one network can report to the same Panel.

If your public IP changes, your Panel will change.

You can set your own Custom Panel with the custompanel parameter.

NOTE! After any changes to custompanel wait 15 minutes for it to update, or run putconf; sleep 2; update; on the ASIC.

Deleting/Removing ASICs from your Panel

Automatic Removal

  1. Adjust the panelclear parameter as described in Writing your Config.
  2. Wait for the ASIC expiration time. You can hover over the ❌ on your Panel to see how many days until your ASIC disappears.
  3. ASICs that had an old ASICseer version installed will be removed after panelclear + another 10 days.

Manual Removal

  1. At the top of your Panel, select the checkbox next to the ❌
  2. Select "remove units" in the dropdown menu.
  3. Paste the resulting line beginning with global remove into your Remote Config File.
  4. In 10 minutes, those ASICs will be removed from your Panel.

NOTE: You can adjust the ASICIDs in the global remove line to suit your preferences.

Forcing Remote Config and Panel Sync

Sometimes, you may need to sync your Remote Config File to your ASICs.

For Single ASICs

Navigate to your Miner Configuration page and click the sync config and panel button.

For Multiple ASICs

  1. Enter a Remote Config File:
  2. Copy-paste the following Installer Code into your multi-ASIC installer box:
    curl -s -k https://install.asicseer.com/netsync/a/https://asicseer.com/config.txt | sh

NOTE: This is an intensive script and is not meant to be run regularly.

Updating to the Latest ASICseer Version

It is highly recommended that you keep global autoupdate yes in your Remote Config File. The ASICseer team drops support for all previous ASICseer versions as soon as a new update is released, in line with an aggressive development schedule. If any issues occur with previous versions, no support will be provided until you update.

NOTE: There is no difference between updating and installing ASICseer. You can always update by reinstalling ASICseer.

If some ASICs miss their update, update them by either reinstalling ASICseer or by using the below methods:

Example of autoupdating only ASICs that need the latest version:
curl -s -k https://install.asicseer.com/netdeploy/a/autoupdate/admin/10.8.250-252.0-255 | sh

Example of forcing autoupdate for all ASICs regardless of version:
curl -s -k https://install.asicseer.com/netdeploy/a,force/autoupdate/admin/10.8.250-252.0-255 | sh

For faster scanning: edit only the last two VLAN octets.

Importing a CSV of your Panel into Google Sheets

  1. Open the ASICseer API Example Sheet.
  2. This opens a read only sheet. To be able to edit, select 'File' -> 'Make a Copy' in the top left and click OK.
  3. Edit the A2 cell to reflect your 6-digit Panel name.

Note: Google Sheets does not support native authentication. If you have a panelpass specified, add your panelpass in cell B2

Using JSON API to load per-Panel or per-ASIC Data

Using historical API

The following API endpoints can load historical monthly per-Panel and per-asic data, useful for enterprise-class customer billing purposes.


examples using 11 (the last month):

How to load ASICseer API data in Google Sheets

  1. Open the ASICseer API Example Sheet (this example has an JSON loading function in the 'Tools' -> 'Script Editor' menu item).
  2. This opens a read only sheet. To be able to edit, select 'File' -> 'Make a Copy' in the top left and click OK.
  3. Select one of the API tabs at the bottom.
  4. Edit the A2 cell to reflect your 6-digit Panel name.

Note: Google Sheets does not support native authentication. If you have a panelpass specified, change the D2 to the below:


Using Nicehash for Mining without a Pool Account

If you don't want to set up any pool accounts, you can use Nicehash.

  1. Replace the pools in your config with the below stanza.
  2. Replace the predefined stratum server locations if necessary.
  3. Your username is your wallet address, replace it with your own wallet address.
global poolname1 sha256.usa.nicehash.com:3334
global username1 15tXyQAYyiD4q1FUVcsdMgG78fFZG6J9zD
global poolpass1 x
global sendworker1 yes
global poolname2 sha256.eu.nicehash.com:3334
global username2 15tXyQAYyiD4q1FUVcsdMgG78fFZG6J9zD
global poolpass2 x
global sendworker2 yes
global poolname3 sha256.hk.nicehash.com:3334
global username3 15tXyQAYyiD4q1FUVcsdMgG78fFZG6J9zD
global poolpass3 x
global sendworker3 yes

Securing your ASIC with Passwordless Login and Public Key

To secure your ASIC and to prevent unauthorized logins, you should use passwordless public key authentication.

WARNING: This procedure disables your password login, so be absolutely sure that your key pair works. Test this procedure with a new Remote Config File on a SINGLE ASIC before using your existing Remote Config File. Keep the SSH session running while you test.

  1. Generate an SSH key pair (instructions for linux and windows).
  2. Add your public key to your Remote Config File like pubkey ssh-rsa AAAAB3gZk1XXXXXX...XXX (only one pubkey per Remote Config File).
  3. Install (or re-install) ASICseer. NOTE: As a security precaution, public key installation occurs only during ASICseer installation.

Using SSH to Login to ASICs from Windows

  1. Connect your computer to the same network as your ASICs.
  2. Download Putty from http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe.
    Putty is an executable that can be run without installing.
  3. Find the IP of your ASIC.
    You can find your ASIC IP on your asicseer.com Panel or on your router's DHCP client table.
  4. Open Putty and input ASIC Information.
    Type the ASIC's IP into Host Name. Port should be 22. Click Open.
  5. Login to ASICseer terminal.
    When the terminal window shows up, login with username root, password admin.
  6. A list of available commands will appear.

Pasting Text: In Windows, CTRL+C to copy text. In putty, SHIFT+INSERT to paste it.
To SSH remotely: Connect to a dedicated VPN box on your ASIC network using your favorite vpn software.

List of Common ASICseer Terminal Commands

ASICseer | available commands:

dmesg		show kernel log
helpme          show this list of commands
gethelp         generate a diagnostics file for getting support
df | p          send output of piped (ex: df) to paste server
update          force a stats update to the panel server
putconf         redownload the contents of your remote config
rawstats        display non-formatted system info / miner stats
jsonstats	display json-formatted system info / miner stats
pool		display recommended pool statistics

Clearing your ASIC's MAC address to Prevent Conficts

In large farms, there are sometimes conflicting MAC address that result in multiple ASICs appearing as if they are one. This results in arp conflicts, incorrect reporting, etc.

If you see multiple ASICs with the same MAC address, you should regenerate the MAC address on your ASIC and then reboot it:

rm /config/mac && sync && sleep 1 && reboot

Identifying Faulty Hashboards

Many people who install ASICseer are surprised to see faulty hashboards. These faulty hashboards existed before you installed ASICseer, you just did not know about them. You can verify this by checking your pool-side hashrate for any individual worker.

If your ASIC has identified a faulty hashboard, it will show a 🔗 or 🔘. You can identify the faulty hashboard using the Panel and the [ | ] hashboard detection symbols.

The below symbols identify which hashboard is detected and working fine from the exhaust side.

If your ASIC shows a 🔗, it indicates a high chain xtime.

If your ASIC shows a 🔘, it indicates a broken hashboard.

Using the Global Hashrate Viewer

If you manage many different Panels, you can set a company name to track hashrates across all of them.

  1. Add global customer yourcompanyname to your Remote Config File (use the same string on all Remote Config Files that you manage).
  2. Wait 20 minutes for the change to propagate.
  3. Enter the companyname you used:

Reverting Braiins OS to Factory Firmware

Braiins OS is not compatible with existing installation methods. In order to install ASICseer on ASICs running Braiins OS, follow the below guide:

  1. Enter a Remote Config File:
  2. Copy-paste the following Installer Code into your multi-ASIC installer box:
    curl -s -k https://install.asicseer.com/net-no-braiiner/a,pos/https://asicseer.com/config.txt | sh

Controlling Power Usage based on Time of Day

If your facility has special requirements for time-of-day power usage, you can use a php script to serve your config file to your ASICs.

  1. Set up your own Remote Config File Server.
  2. Run: mkdir -p /var/www/html/config && curl -o /var/www/html/config/index.php http://p.asicseer.com/raw/omcpl
  3. Run: nano /var/www/html/config/index.php to edit your script.
  4. Reinstall your ASICs using your Remote Config Link: http://ip.of.your.server/config/

Uninstalling ASICseer and/or Restoring to Factory Settings

Using the IP Report Button

Use the "Restore via IP Report Button" functionality as described on Point 3 of the Bitmain© factory restore guide.

Using the WebUI firmware Upgrade Page

  1. Download the correct Bitmain© firmware for your ASIC.
    NOTE: Be careful, any Bitmain© firmware described as having a "security" or "secure" firmware actually prevents SSH to your ASIC.
  2. Navigate to your ASIC's firmware upgrade page and upload the Bitmain© firmware to your ASIC.

NOTE: This will restore all settings and pools to factory settings.

Powerful and Advanced

  1. Enter a Remote Config File:
  2. Use the below uninstaller code:
    Single: curl -s -k https://install.asicseer.com/deploy/a,stock,saveconf/https://asicseer.com/config.txt | sh
    Multiple: curl -s -k https://install.asicseer.com/netdeploy/a,stock,saveconf/https://asicseer.com/config.txt | sh

Get Immediate 24/7 Support via Telegram

Free 24/7 support: Free lifetime support 24/7 via the ASICseer Telegram channel.


Contacting the ASICseer Team

Please direct all Media and Business inquiries to info@asicseer.com

Emails requesting technical support will be treated as spam. Get Immediate 24/7 Support via Telegram.

© 2019       ASICshack logo       All rights reserved.