TCMinerSystem puts a mining pool proxy and a device console in one box

The default credentials are the first thing to change

Before anything else in the documentation, there is an important callout, and it is the most practically useful paragraph in the README.

The default administrator account is `qzpm19kkx` and the default password is `xloqslz913`. The instruction is to change the account, the password and the web access port immediately after the first login, and to restrict access to the management port through a firewall.

Publishing default credentials is a legitimate practice for a self-hosted console, because the installer has to give you something to log in with, but it only works if the software is not reachable before you change them. That makes the firewall rule the critical part: if the management port is exposed to the internet on a fresh install, the default password is the security of the whole farm.

The same instruction appears in the Windows section, where the step list ends with changing the default account, password and web access port on first login. The repetition is a good sign about how the author thinks about it.

The rest of the product is a mining operations system. It is described as a pool proxy and operations management system for mining machines, mining farms and pool nodes, usable to connect to traditional pools, to centrally manage and forward ports, and to build your own pool node depending on what the business needs.

The interface is a web console. Through the browser you can view devices, ports, hashrate, logs, versions and system running status, and there is an animated preview of the management backend in the README.

Two deployment shapes, traditional pool and own node

The core capabilities table lists six things, and the first two are the two ways you can use the system.

Traditional pool proxy means centrally managing miner connections, forwarding ports and the target pool, which simplifies bringing many devices online and the daily operations around them. Private pool node means building your own pool node according to your business needs, which suits mining farms, node service providers and cases where you own the compute.

The distinction is not just a feature toggle. A traditional pool proxy is a traffic forwarder that many miners point at, and its value is in the operational surface: one place to see which machines are connected, which ports are open, and where the hashrate is going. A private pool node is the same machinery pointed at a pool you operate, which changes who bears the responsibility for uptime and for the block distribution.

The third capability is hashrate and fee management, providing hashrate statistics, allocation rules and custom fee rate configuration so you can observe and manage how the business is running. The fourth is secure transport through the companion TMS client, which completes encrypted and compressed transfer to reduce bandwidth pressure and link exposure.

The fifth and sixth are about deployment and visibility. Multi-platform deployment provides Linux and Windows executables plus a Linux installation tool for quick deployment and updates. The web management console is the browser view described above.

For the documentation, each scenario has its own entry point in a GitBook documentation site, with separate tutorials for connecting to a traditional pool and for standing up a pool node.

The companion TMS client handles the encrypted and compressed link

The secure transport piece is a separate project, and the README treats it as a companion rather than a module.

TMS is described as a local security client supporting encrypted and compressed transmission, which can reduce public network connection and bandwidth pressure and improve link security. The README asks you to read the service agreement before you start using it, and the TMS project itself lives at the MinerProxyPro/TMS repository, linked separately from the main documentation.

Why a separate client makes sense here: a miner sitting in a remote location with a poor uplink is the constraint that matters, and compressing the stratum traffic before it leaves the site reduces both bandwidth and the amount of time the link is exposed. Putting that in a small local client means the miner side stays simple, and the fleet side does the accounting.

The same reasoning explains the deployment list. Linux and Windows executables cover the two places miners actually run, and the Linux installation tool is a menu-driven script that handles install, update, start, stop and port configuration, so an operator updating a box does not need to remember a sequence of commands.

The project is Rust, MIT licensed, with the last push on 2026-10-20 and releases 6.4.0, 6.3.4 and 6.3.3 through August and October 2026. The homepage is tcminersystem.com, and the documentation is a GitBook site with English, Simplified Chinese and Russian versions linked from the README.

Installing on Linux is a piped script, with a mirror for slow links

The Linux install is one command, and the README is careful about the case where GitHub is slow from your region.

On Ubuntu, in a Bash terminal, run the following command to open the installation tool menu:

bash <(curl -s -L https://github.com/mine-Proxy/TCMinerSystem/raw/main/install.sh)

And if accessing GitHub is slow from your region, there is an alternative address:

bash <(curl -s -L https://cdn.tcminersystem.com/mine-proxy/TCMinerSystem/raw/main/install.sh)

After the installation tool starts, you complete the install, update, start, stop and port configuration from the menu it presents. Ubuntu is the recommended platform, and the mirror is a sensible accommodation for a product whose users are distributed across regions with uneven network access to GitHub.

The Windows path is manual by design, and it is a five step list. Open the project's windows directory. Choose the latest version of the `tcstminersystem-*.exe` file. Go into the file page and click `View raw` to download the program. Double click and run it, following the terminal prompts to open the management backend in your browser. And change the default account, password and web access port immediately after the first login.

That third step, clicking View raw on the file page, is the GitHub interface for downloading a large binary, and the README is explicit about it because the usual download link is the one people try first and then get stuck on.

Transparent access is offered, and tightly restricted

There is a section about transparent access to authorised networks, and it is worth reading closely because it describes a capability that could be used badly.

If you are responsible for mining farm operations, or have obtained administrative authorisation for the relevant farm routers and devices, you can contact the project to evaluate a DNS or transparent proxy access solution, in order to reduce the work of modifying miner configuration one device at a time.

And then the warning: transparent access is limited to network environments where the device owner is explicitly informed and has authorised it. The instruction is not to hijack, forward or divert devices, hashrate or network traffic that do not belong to you or that you are not authorised for.

This is the exact capability that makes a mining proxy dual-use. A transparent proxy in front of a farm means the miners need no configuration change at all, which is enormously convenient for an operator and enormously attractive for anyone who wants to redirect somebody else's hashrate. The project draws the line explicitly, and the README's separate service agreement section reinforces it, which is the right posture for a tool in this category.

For an operator evaluating it, the practical point is that the line is drawn in the network, not in the software. If you run a transparent deployment, you need the authorisation to be real and documented, because the difference between a legitimate farm operator and a hijacker is entirely in who owns the routers and whether they said yes.

Coin support varies by version, and the terms are specific

Two things in the closing sections deserve attention before anyone installs this.

The first is algorithm and coin support. The documentation is explicit that TCMinerSystem's algorithm and coin support will change with version updates, and that the table shown is a set of common examples from the project documentation, with the actual support range to be confirmed against the current version's console and the official documentation.

The listed examples map algorithms to typical coins: SHA256 for BTC and BCH among others, ETHASH for ETC, ETHW, ETHF and the combined ZIL variants, SCRYPT for LTC among others, and KHEAVYHASH for KASPA among others.

The second is the service agreement, and it is unusually specific for an open source project. TCMinerSystem is regulated by Hong Kong law, and the caution notes that different countries or regions may impose different restrictions on digital currency, mining machine management and pool services, so you should confirm that the relevant activity is lawful where you are.

The product nature section states that this product is positioned as an operations management tool for mining machines, farms and pool nodes, that it is not a VPN tool, and that it does not provide the ability to bypass network access restrictions. All connected devices must be actively configured by the device owner or by a manager with explicit authorisation, and it is not permitted to obtain, control or divert other people's devices, data or hashrate by improper means.

The user admission criteria then list five conditions you confirm by using the service, including that you are not listed as a terrorist organisation or terrorist actor by bodies such as the UN Security Council, that you are not restricted or prohibited from using the program by administrative, judicial or law enforcement authorities, that you are not a resident of Cuba, Iran, North Korea, Syria or other sanctioned regions, that you are not a resident of a country where digital currency activity is prohibited by law or policy, and that your use of the program complies with local laws, regulations and policy.

Editorial conclusion

Adopt TCMinerSystem if you operate a fleet of mining machines and want one place to manage ports, hashrate allocation, fee rules and a self-hosted pool node, since that is the whole product. Skip it if you run a single machine, since the console and the proxy earn their keep only at fleet scale, and be careful with the transparent DNS or proxy access path, which the documentation restricts to networks where the device owner has explicitly authorised it. Verify first that you change the default administrator credentials and the web access port before the box is reachable from anywhere, that the algorithm and coin support in your version covers what you mine, and that your use complies with the service agreement and local law, since the project is regulated by Hong Kong law and carries explicit user admission criteria.

Frequently asked questions

Official sources

1. License: MIT
2. mine-Proxy/TCMinerSystem on GitHub
3. Project website
4. README
5. Releases