RustMinerSystem: A Rust miner proxy and pool-node front end for farms

What RustMinerSystem does for miners, farms and pool nodes

RustMinerSystem is a Rust program that sits between mining hardware and a pool. The README describes two modes. In the first, it proxies a traditional pool: miners connect to RustMinerSystem, which manages connections, ports and forwarding policy on their behalf. In the second, the machine running it becomes a pool node itself, which the README frames as suitable for node operators, farm operators and self-run business scenarios.

The intended audience is not a hobbyist with one ASIC. The feature table lists custom fee rates for raising site or node operating revenue, a visual admin panel for checking run status, ports and miners, and multi-platform packages covering Linux, Windows, ARM and ARMV7. Those are operator concerns: many devices, many ports, and a fee layer between them. A companion project, RMS, is a local client that the README says encrypts and compresses traffic to reduce bandwidth pressure and protect the link. The repository also ships excel端口导入模板.xlsx, a spreadsheet template for importing ports in bulk, which tells you the expected scale is dozens or hundreds of entries, not two.

The proxy and node architecture visible in the repository

The top level of the repository separates the moving parts: APP/ and CLI/ hold the application and command-line code, linux/ and windows/ hold platform packages, and install.sh, arm-install.sh and armv7-install.sh are the installers. The README does not publish an internal module diagram, so the data flow has to be read from behaviour rather than source: miners point at a RustMinerSystem port, the program forwards to a traditional pool or acts as the pool endpoint, and the web admin panel reads and writes the connection, port and fee configuration.

That architecture has one clear consequence. RustMinerSystem is a stateful middlebox. Every miner's share traffic passes through it, so its process must stay up and its configuration must be correct before miners are pointed at it. The README's emphasis on an install menu with start, stop, port changes and boot autostart is consistent with that: this is software you run as a service, not a script you invoke per connection. The RMS client adds a second hop when used, trading CPU and a client install for encrypted, compressed transport. If you skip RMS, the README gives no indication that the link between miner and proxy is protected.

Installing RustMinerSystem on Linux and opening the admin panel

The README recommends Ubuntu and provides a one-line installer that opens an interactive tool menu. Run it as a user who can install services:

bash <(curl -s -L https://github.com/EvilGenius-dot/RustMinerSystem/raw/main/install.sh)

If GitHub is slow from your region, the README offers a mirror. Note the -k flag, which disables certificate verification for that host:

bash <(curl -s -L -k http://static.rustminersystem.com/EvilGenius-dot/RustMinerSystem/raw/main/install.sh)

ARM and ARMV7 machines have their own scripts, arm-install.sh and armv7-install.sh, fetched the same way. After the script runs, the README says a menu appears where you select install, update, start, stop, change port or set boot autostart. Once started, open the admin panel in a browser. The README states the default account is qzpm19kkx and the default password is xloqslz913, and asks you to change both the credentials and the web access port soon after the first login.

On Windows the README gives no installer command. It directs you to the windows directory, where you pick the newest rustminersystem-*.exe, click View raw to download it, then double-click the program and follow the terminal prompt to reach the admin panel in a browser. The first real use after that is the same on both platforms: add a forwarding entry for your pool, point a miner at the RustMinerSystem port, and watch the miner and connection status in the panel.

Default credentials, a closed binary and the service agreement

The first limitation is printed in the README itself. RustMinerSystem ships with a known default admin account and password, qzpm19kkx and xloqslz913, and a default web port. Anyone who reaches the panel before you change them has the same access you do. The README treats this as a first-login task, not a hardening step, and there is no documented forced password change or first-run setup wizard.

The second is distribution. The Linux path installs from a shell script and the Windows path hands you a prebuilt .exe from the repository. The repository is MIT licensed, but the README does not describe a build-from-source path for the proxy itself, and the presence of APP/, CLI/, linux/ and windows/ directories does not by itself tell you that a reproducible build of the shipped binary is documented. If your adoption policy requires auditing the code you run, that gap matters more than the licence.

The third is legal and operational. The README carries a caution that RustMinerSystem is regulated under Hong Kong law and that different countries or regions may restrict this kind of product or service, and it points to a separate service agreement. Fee configuration is a stated feature, and on a farm that means the relationship between the operator and the miners being pointed at the proxy is a policy question, not a technical one. Read the agreement before deployment, and treat the supported coin and algorithm list as fluid: the README says it changes with version and configuration hot updates, so a coin that works today is not a guarantee for the next release.

RustMinerSystem compared with a plain stratum forwarder

The obvious alternative for many operators is a minimal stratum forwarding proxy: a small program that listens on one port and relays to one pool, usually with no web interface, no fee configuration and no node mode. The difference in approach is scope. A plain forwarder has one job and a small attack surface, and you can read its whole configuration in a few lines. RustMinerSystem instead bundles connection and port management, a browser admin panel, fee configuration, multi-platform packaging, bulk port import via a spreadsheet template and an optional encrypted transport through RMS.

That bundle is the product. If you are running a single rig against a single pool, the extra surface buys you nothing and costs you a service to maintain, a panel to secure and an upgrade cycle to track. If you are running a farm with many ports, several pools and a need to see miner and connection status in one place, the alternative means assembling that from scripts and dashboards yourself. The trade is not performance, which the README does not quantify, but operational scope. Choose RustMinerSystem when you want the management layer; choose a plain forwarder when you want to forget the proxy exists.

Release cadence, upgrade cost and the MIT licence

The release history is dense. Version 6.3.0 was tagged on 2026-09-20, 6.2.0 on 2026-09-13 and 6.1.1 on 2026-09-10, and the last push to the repository was on 2026-09-20. Three releases in ten days means you should expect to update often if you want fixes, and the install menu includes an update option for that reason. The upgrade cost is not just the download: because the proxy is stateful, an update is a restart of the process that all your miners depend on. The README does not document rollback, so plan how you would return to a previous version before you need it.

The licence is MIT, which is permissive and places few obligations on how you use or redistribute the code. That covers the repository. It does not resolve the separate service agreement, which the README says is governed by Hong Kong law and which you should read on its own terms. The README also notes that the documentation and supported algorithm list are maintained on GitBook rather than in the repository, so the README you are reading is a summary, not the full manual. For a farm, the practical licence question is not redistribution but whether the fee configuration and the service agreement match what you tell the people whose hashrate passes through the proxy.

Editorial conclusion

RustMinerSystem suits operators who already run miners and want a single proxy layer for connection management, fee configuration and status monitoring, on Linux, Windows or ARM. It is the wrong tool if you only need a one-line forwarder, if you cannot accept a closed binary with a default admin account, or if the Hong Kong service agreement conflicts with your jurisdiction. Before deploying, verify three things: that the release tag you download matches the version you intend to run, that the default admin credentials qzpm19kkx / xloqslz913 and the web port have been changed, and whether a self-built pool node is actually supported for your coin and algorithm, since the README says the supported list changes with version and configuration hot updates.

Frequently asked questions

Official sources

1. EvilGenius-dot/RustMinerSystem on GitHub
2. License: MIT
3. Project website
4. README
5. Releases