# TCMinerProxy ships its default admin password in the README

> A Rust Stratum mining pool proxy with a web panel, a configurable revenue cut and a curl-to-bash installer. Two details deserve attention before you deploy it: the published default credentials, and a fallback install URL that passes the -k flag to curl.

**MinerProxyPro/TCMinerProxy** — MinerProxy矿池抽水 矿池代理 矿池中转 矿池抽水  纯中转Rust全新独立架构矿池中转 / 算力抽水工具 TCMinerProxy；近年全球大型矿场主流 Stratum 矿池代理，支持算力分流、自建私有矿池、TMS 加密隧道，适配全币种比特币挖矿等POW 算力运维软件Bitcoin Mining Farm Management。

- Repository: https://github.com/MinerProxyPro/TCMinerProxy
- Website: https://www.tcminerproxy.com
- Stars: 998 · Forks: 28
- Language: Rust
- License: MIT
- Published: 2026-09-17 · Updated: 2026-09-17 · Language: en
- Canonical page: https://hysenlabs.com/projects/minerproxypro-tcminerproxy

## The default account and password are printed in the README

An IMPORTANT callout near the top of the document names the panel defaults in plain text: the account is `qzpm19kkx` and the password is `xloqslz913`. It then tells the reader to change both, plus the web access port, as soon as the first login succeeds. That is the right instruction, and it is also the kind of detail that gets screenshotted into a ticketing system, so treat those two strings as burned. The reminder matters more than usual here because the panel exposes what the README calls a full-dimension view: program state, port occupancy, online miners and hashrate flow. Anything that tells an operator how much compute is pointed at a node is worth protecting before it is exposed on a routable address.

## The fallback installer runs curl with -k

The recommended Linux path pipes a remote script into bash:

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

A second block exists for regions where GitHub is slow, and it reads `bash <(curl -s -L -k https://cdn.tcminerproxy.com/MinerProxyPro/TCMinerProxy/raw/main/install.sh)`. The `-k` flag tells curl to accept any certificate, so that path is no longer verifying that the response came from the host it claims. Running a script fetched that way is a different decision from running the GitHub one, even though both end in bash. The first URL points at the repository itself. The second points at a vendor CDN and turns off the check that would tell you the two differ. Ubuntu 20.04 or newer is the stated baseline for either route.

## The fee cut is a configurable dial, not a hidden charge

One row in the capability table is the one most operators will care about: a self-set revenue percentage, described in the source text as widening the operating margin for farms and node providers. That framing matters. The proxy sits between your miners and a pool, so whoever runs it decides what share of the output it keeps. There is no upstream taking a percentage on your behalf, and there is no published default rate to argue with. The same transparency applies to the role the tool claims: it can relay to traditional pools, and it can also turn one of your own devices into a pool node. Both modes are described as first-class, which means the same binary that proxies for you can host for you.

## Relaying a traditional pool and hosting your own node are one binary

The stated purpose covers three jobs in one: proxying traditional pools, relaying traffic, and making a device act as a genuine pool node. The first is framed as a one-stop connection to mainstream pools with centralised handling of the connection channels for every machine on the network, port allocation, and forwarding rules, aimed at batch maintenance. The second is for private deployments by node providers, large physical farms, or in-house compute businesses. The third is the web panel, where you watch program state, occupied ports, online miners and hashrate flow from a browser. Deployment is described as covering Linux, Windows, ARM and ARMV7, each with a one-click script and a complete install package, so the operational story is the same on a rack server and on a small single-board box.

## TMS lives in another repository and carries the transport protection

Encryption and compression for the link are not in this repository. They sit in TMS, a local client published separately, which the README credits with three layers of protection: data encryption, traffic compression, and link security, framed as the answer to hashrate hijacking and eavesdropping. The compression claim carries a second benefit the source text puts plainly, lower bandwidth pressure, which on a farm with thousands of miners crossing a metered link is the number that decides whether the feature gets turned on. If you are evaluating TCMinerProxy as a single component, note that the transport guarantee is a two-repository dependency. The companion client is linked from the feature table, the documentation index and the header links, in all three places, and the Windows path here does not mention it at all.

## Twenty-two algorithms, and a support list that moves with the version

The coin coverage is presented as a collapsible table with an explicit caveat that algorithms and coins are hot-updated along with the version and configuration, so the list is a snapshot rather than a contract. What the snapshot contains runs from SHA256 through BTC, BCH and SPACE, to ETHASH carrying more than twenty coins including ETC, several ZIL combinations and ETHW variants, down to RANDOMX for XMR and ZEPH, KHEAVYHASH for KASPA, AUTOYKOS2 for ERG, EQUIHASH for ZEN and ZEC, and CUCKATOO32 for GRIN. Twenty-two rows in total. The practical consequence is that a farm hashing any single algorithm can check support before buying hardware, and a farm mixing algorithms has to re-check on every upgrade rather than trusting an old list.

## The service agreement excludes residents of named jurisdictions

The legal section is not boilerplate boilerplate-free: it opens by stating the project is regulated under Hong Kong law and warns that local requirements differ by country and region. The admission criteria then enumerate five conditions, and one of them bars residents of Cuba, Iran, North Korea, Syria and various sanctioned jurisdictions. Another bars residents of regions where digital currency business is prohibited by law, and the source text names mainland China as an example. Liability terms place the full legal consequence on the user where local law makes the activity non-compliant, waive the right to bring claims against the project, and treat downloading and running the software as acceptance. The document also states the product is not a VPN and cannot reach restricted networks, and that every miner must be configured by its own owner.

## Three releases in twelve days, on a six-week version cadence

The release history shows steady movement rather than a single launch. Version 6.1.0 was published on 2026-09-09, 6.2.0 on 2026-09-15, and 6.3.0 on 2026-09-21, with the last push to the repository dated 2026-09-26. Read the dates together with the hot-update caveat on the algorithm table: an operator upgrading between releases is also taking a new coin list, and the release notes become the place to check what moved. The Windows route in the documentation reflects the same rhythm, since it points at a `windows/` directory and tells you to take the newest `tcminerproxy-*.exe`, click `View raw`, then double-click and follow the terminal. There is no checksum step in those instructions, so verifying the download means checking the release asset yourself.

## Conclusion

Treat TCMinerProxy as infrastructure for a farm you already control, and change the admin account, password and web port before the first login rather than after. The tool is worth a look if your operation runs Stratum across several lines and you want one panel for port allocation, online miners and hashrate flow, but three things decide it. First, the fee cut is a dial you set, so read the terms again before pointing other operators at your node. Second, TMS is a separate client in a separate repository, and running without it means running without the encryption and compression the documentation describes. Third, the license gate excludes residents of several named jurisdictions including mainland China, so check that before anything else if you are outside Hong Kong, where the project says it is regulated.

## FAQ

### What is the default admin password for TCMinerProxy?

The documentation names the defaults as account `qzpm19kkx` and password `xloqslz913`, and instructs the reader to change the account, the password and the web access port after the first login. Because they are published, they should be treated as already known to anyone who has read the page.

### How do you install TCMinerProxy on Linux?

On Ubuntu 20.04 or newer you run `bash <(curl -s -L https://github.com/MinerProxyPro/TCMinerProxy/raw/main/install.sh)`. The script then presents a menu with install, update, start, stop, change port and enable start on boot options. A fallback URL on the vendor CDN is offered for slow GitHub access and passes `-k` to curl, which disables certificate verification.

### Can TCMinerProxy act as its own mining pool?

Yes. Beyond relaying traffic to traditional pools, the project describes letting one of your own devices act as a genuine pool node, aimed at node providers, large physical farms and in-house compute operations. Both roles ship in the same tool.

### Which mining algorithms and coins does TCMinerProxy support?

The documented table covers twenty-two algorithms including SHA256, ETHASH, RANDOMX, KHEAVYHASH, EQUIHASH, AUTOYKOS2 and CUCKATOO32, with coins attached to each row. The project states that the list is hot-updated along with the version and configuration, so treat it as a snapshot rather than a fixed guarantee.

### What does the TMS client add to TCMinerProxy?

TMS is a separate local client published in its own repository. It is credited with encrypting and compressing the data in transit, which reduces bandwidth pressure and adds link security on top of the proxy, and it is described as protection against hashrate hijacking and eavesdropping.

## Sources

- [License: MIT](https://github.com/MinerProxyPro/TCMinerProxy/blob/main/LICENSE)
- [MinerProxyPro/TCMinerProxy on GitHub](https://github.com/MinerProxyPro/TCMinerProxy)
- [Project website](https://www.tcminerproxy.com)
- [README](https://github.com/MinerProxyPro/TCMinerProxy/blob/main/README.md)
- [Releases](https://github.com/MinerProxyPro/TCMinerProxy/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/minerproxypro-tcminerproxy