TCMinerProxy: a Rust Stratum proxy for mining farms that want their own pool endpoint

What TCMinerProxy does between the miner and the pool

A Stratum miner normally opens one TCP connection to one pool and reports shares on it. TCMinerProxy inserts itself in that path: miners point at the proxy, and the proxy maintains the upstream connection to the pool. The README describes this as 矿池中转 (pool relay) and 矿池代理 (pool proxy), and lists the jobs it covers as 接入、转发、管理、费率配置和状态观察: onboarding, forwarding, management, fee configuration and status observation.

The audience is explicit. The project is aimed at 矿机、矿场、矿池节点和多线路运维场景: mining machines, farms, pool nodes, and multi-route operations. That is a different user from someone running one GPU at home. The repository also supports 私有化矿池节点搭建, deploying a private pool node, which the README frames around node operators, large physical farms and businesses with their own hashrate.

One capability deserves a plain description rather than a euphemism. The README lists 灵活自定义抽水费率, a configurable fee or hashrate cut, as a core capability. That means the operator decides how much of the hashrate passing through is redirected before it reaches the upstream pool. This is a deliberate, documented feature of the product, and anyone evaluating it should treat it as such rather than discovering it later.

Rust, Stratum forwarding and the TMS tunnel

The primary language is Rust, and the project describes its architecture as 纯中转Rust全新独立架构, a relay-only design on a new independent Rust codebase. The relay role matters: the proxy is not a miner, it does not hash, and it does not need a GPU. It terminates Stratum connections from miners and opens its own connections upstream.

The second component is TMS, a separate local client repository linked from the README. The documentation says TMS handles 加密与压缩传输数据, encrypting and compressing the transmitted data, and describes it as reducing bandwidth pressure while hardening the link. The threat it addresses is named in the capability table: 算力劫持 (hashrate hijacking) and 数据窃听 (data eavesdropping) on the wire between the farm and the pool. If your miners talk to an upstream pool over a path you do not control, that is the case for running TMS at both ends.

Protocol coverage is broad rather than Bitcoin-only. The README's algorithm table spans SHA256 for BTC, BCH and SPACE, ETHASH for ETC, ETHW and a long list of forks, plus SCRYPT, KHEAVYHASH, BLAKE2S, EQUIHASH, RANDOMX, KAWPOW and others. The README states that supported algorithms and coins update with versions and configuration, so treat that table as a snapshot of the documentation rather than a frozen contract.

Installing TCMinerProxy on Linux and reaching the console

The README recommends Ubuntu 20.04 or newer and provides a menu-driven installer. Run the command below, and the installer presents options for install, update, start, stop, changing ports and enabling start on boot.

bash <(curl -s -L https://github.com/MinerProxyPro/TCMinerProxy/raw/main/install.sh)

If GitHub is slow from your location, the README gives a mirror on the project's own CDN. The command is identical apart from the URL; verify that the script you fetch matches the repository copy before running it as root.

bash <(curl -s -L -k https://cdn.tcminerproxy.com/MinerProxyPro/TCMinerProxy/raw/main/install.sh)

On Windows, the README points to the windows directory in the repository, where you pick the newest tcminerproxy-*.exe, open the file page, click View raw to download it, then run the executable and follow the terminal prompt to the web console in a browser.

Before the first login, note the credentials the README publishes. The default account is qzpm19kkx and the default password is xloqslz913, and the README's own warning is to change both the account password and the Web access port as soon as possible. A published default password on a panel that controls hashrate routing is the single most obvious thing to fix on day one.

Where TCMinerProxy is the wrong tool

The README does not document rollback. The installer menu includes update, and releases are frequent (6.0.0, 6.1.0 and 6.2.0 within about two weeks in August and September 2026), but nothing in the README describes how to revert to a previous binary if an upgrade breaks a port mapping or a fee rule. On a live farm that is a real operational gap, and it argues for testing an upgrade on one machine before touching the rest.

The project is also not a mining application. Nothing in the README describes generating hashrate, joining a pool as a worker for a single user, or a graphical miner. Search interest around this name leans toward consumer mining apps, and that is a mismatch: TCMinerProxy is plumbing for people who already have machines.

There is a licensing and jurisdiction boundary too. The README's service agreement states the software is governed by Hong Kong law, that it is not a VPN and cannot reach restricted network resources, and that users must confirm their own jurisdiction allows digital currency and pool proxy activity. It also lists user eligibility conditions that exclude people on UN sanctions lists and residents of certain countries. The README does not spell out what happens to the panel if you operate outside those terms.

Finally, the fee feature is a governance question, not a technical one. If you are a hosting provider or a farm manager, running a hashrate cut on someone else's machines without their knowledge is a contractual and legal problem regardless of what the software permits. The README presents the fee rate as an operator setting and says nothing about disclosure.

How TCMinerProxy differs from a general-purpose TCP proxy

The obvious alternative is a generic reverse proxy such as HAProxy or nginx in stream mode, or an SSH tunnel. Those tools forward bytes and do nothing else. They will not parse Stratum, so they cannot show you per-worker hashrate, cannot apply a per-connection fee setting, and cannot tell you which miner dropped off.

The difference is the Stratum-aware session model. TCMinerProxy keeps track of 在线矿工 (online miners), 端口占用 (port usage) and 算力流水 (hashrate flow) in its web panel. A generic proxy gives you connection counts and byte totals; it has no concept of a share. That gap is the whole reason this class of software exists.

Against the TMS tunnel specifically, the comparison is a plain encrypted tunnel like WireGuard or stunnel. Those encrypt the path but do not compress Stratum traffic, and they do not understand the protocol either. The README describes TMS as combining encryption, compression and link protection, which is a narrower and more mining-specific claim. If your only requirement is confidentiality on the wire, a general tunnel is simpler and better understood. If you want the compression and the integration with the proxy's own connection handling, TMS is the option the project actually supports.

Licence, maintenance and what an upgrade actually costs

The repository is MIT licensed, which is permissive: you can use, modify and redistribute it, including in commercial farm operations, provided the copyright notice and licence text are preserved. Note that the licence covers the code, not the service relationship. The README separately links a 服务协议 (service agreement) and a 免费定制 (free customization) page on the project site, and the agreement carries its own eligibility and jurisdiction terms. That is a contract layered on top of the code, and it is worth reading before you deploy at scale. Nothing here is legal advice; if you operate commercially, have someone qualified read the agreement.

Maintenance looks current rather than dormant. The last push to the default branch was on 2026-09-15, the same day as the 6.2.0 release, and 6.1.0 and 6.0.0 landed on 2026-09-09 and 2026-08-31. The release cadence is fast, which cuts both ways: fixes arrive quickly, and so does churn. The README does not publish a changelog inside the repository beyond the Releases page, and it does not describe a deprecation or migration policy for configuration between major versions.

Upgrade cost, as far as the README shows, is the installer menu plus a restart. The README documents install, update, start, stop, port changes and boot autostart through that menu, and gives no separate migration step. Plan for the panel to be briefly unavailable during an update, and keep the previous binary if you can, since rollback is not documented.

Editorial conclusion

Adopt TCMinerProxy if you already run miners and want one managed endpoint in front of them, or if you are building a private pool node and need a Stratum front end in Rust. Do not adopt it as a desktop mining application: it has no hashing component, and the README never describes how to mine with it, only how to proxy. Before pointing production hashrate at it, verify the default credentials have been changed, that the Web port is not exposed to the internet, and that the install script from the mirror URL resolves to the same content as the GitHub copy. The service agreement states the software is governed by Hong Kong law and that you must confirm your own jurisdiction permits pool proxy operation.

Frequently asked questions

Official sources

1. License: MIT
2. MinerProxyPro/TCMinerProxy on GitHub
3. Project website
4. README
5. Releases