VIPORMiner: relaying mining rigs to a pool for a fixed 0.2 percent fee

VIPORMiner relays mining hardware to a pool rather than being the pool

VIPORMiner is a proxy layer written in Rust for cryptocurrency mining sites. Mining software on each rig is pointed at the proxy, and the proxy forwards that traffic to a pool on the operator's behalf. The project description frames two possible roles: relaying to an existing traditional pool, or operating as a genuine pool node. Those are quite different jobs, and the second one puts block template handling on the operator rather than on the pool. The repository ships Linux, ARM and Windows payloads, plus a web panel, since the installation notes refer to a default backend account and password. The licence is MIT, the default branch is main, and the repository includes translation directories covering English, Russian and Chinese. This is infrastructure aimed at operators who already own hardware and already have a pool relationship, not at someone looking for mining software.

The developer fee is two tenths of one percent and applies to a single machine

The project description states that the developer fee is fixed at two tenths of one percent, with no minimum number of mining machines, so a single rig pays the same rate as a large farm. The same description claims near lossless forwarding, precise ratio accuracy, a 1000G stress test and support for millions of concurrent connections. Those are the maintainers' own figures rather than independently checked measurements, so treat them as claims to test against your own traffic rather than as sizing guidance. The structure of the fee matters more than its size for planning. Because it is a flat percentage rather than a tier, the cost is easy to forecast, yet on a single machine it is a noticeably larger share of a small payout than it is in a hundred machine deployment. Nothing in the documentation describes a way to turn the fee off.

One binary fronts SHA256, Ethash, RandomX and a long tail of coins

The documentation includes a table mapping mining algorithms to the coins they can be pointed at. SHA256 covers BTC and BCH, ETHASH covers ETC plus a long list including ETHW, ETHF and ZIL variants, SCRYPT covers LTC, KHEAVYHASH covers KASPA, BLAKE2S covers KDA, BLAKE2B covers SC and HNS, OCTOPUS covers CFX, EAGLESONG covers CKB, EQUIHASH covers ZEN and ZEC, RANDOMX covers XMR and ZEPH, KAWPOW covers RVN, AUTOYKOS2 covers ERG, NEXAPOW covers NEXA and ZKSNARK covers ALEO. The documentation also notes that the coin list for a given algorithm is updated over time, so the table shows one moment rather than a fixed contract. The practical consequence for an operator is that a single proxy instance fronts many algorithms, which means you have to confirm that the algorithm your own hardware runs is present before pointing it at the relay. A rig on an algorithm missing from the table simply has nowhere to go.

Installing on Linux is one curl line that pipes install.sh into bash

The installation notes give a single shell command that downloads the installer and executes it immediately. Run it on the host that will act as the proxy; on success it prints a menu that you follow to complete the setup.

      bash <(curl -s -L https://raw.githubusercontent.com/ViporMiner/VIPORMiner/main/install.sh)

Once it finishes, the panel comes up with the default backend credentials qzpm19kkx and xloqslz913. Nothing in the documentation describes how to rotate those, so treat them as public knowledge and change them before the panel is reachable from anywhere but your own machine. For hosts that cannot reach GitHub, the notes point to a mirror on a different domain.

      bash <(curl -s -L -k https://vippool.cn/ViporMiner_install.sh)

That second line passes -k, which skips TLS certificate verification. It is a convenience for a mirror, and it removes the check that the script you are about to execute came from the host it claims to. Read it first if that difference matters to you. Boards with ARM CPUs use a separate installer.

      bash <(curl -s -L https://raw.githubusercontent.com/ViporMiner/VIPORMiner/main/armv7-install.sh)

The repository also carries an arm-install.sh beside it, so on a CPU that is not ARMv7 you need to work out which of the two matches your hardware before running either.

Windows runs from a folder of prebuilt binaries with no installer step

For Windows hosts, the documentation points to a windows directory inside the repository and asks operators to download the version that matches their machine, then start it by double clicking. There is no installer wizard and no documented configuration file to edit beforehand, which makes it the quickest way to stand up a relay and also the easiest to get wrong: an unknown binary launched on a Windows server deserves a check before it goes near production rigs. The same default backend account and password shown for the Linux install appear in the Windows section, so every fresh deployment of this product starts life with identical panel credentials. The repository also carries an Excel port import template, which suggests that port configuration for large fleets is expected to arrive in bulk rather than one machine at a time, and a set of translation directories under i18n that cover the panel interface.

The proxy adds a hop, and the service agreement limits who may use it

Every design decision here has a cost, and the largest one is the extra hop. A rig that talks to the relay stops hashing if the relay host is down or if the network path to it degrades, even though the pool itself is reachable. Pointing the mining software straight at a pool endpoint removes both that dependency and the fee, at the cost of losing the unified view and the bulk port handling the panel provides. The project points at the second alternative itself, becoming a real pool node rather than relaying to one, which is a different operating model with more parts to keep running. Legal scope is also defined narrowly. The service agreement says the product is governed by Hong Kong law, that it is not a VPN and cannot make region blocked content reachable, and that all connected devices must be configured by their own owners. Residents of jurisdictions that restrict cryptocurrency activity, including mainland China, Iran, North Korea, Syria and Cuba, are excluded from use.

MIT licensed, with releases landing in October 2026

The code is released under the MIT licence, which allows redistribution and modification of the client software under its terms, though using the software does not settle what the pool operator's own terms require of the fee arrangement. Maintenance looks current: the last push was on 2026-10-19, and releases v-6.4.0 on 2026-10-19, v-6.3.4 on 2026-10-15 and v-6.3.3 on 2026-10-08 landed in the days around it. The version numbers use a v- prefix with three components, so an operator pinning a build should expect to handle those upgrades rather than a yearly jump. The repository also holds an origin.json file, and support happens over a Telegram group and a QQ group rather than through an issue tracker. Top level files include install.sh, arm-install.sh, armv7-install.sh, a linux directory and a windows directory.

Editorial conclusion

VIPORMiner fits operators running a mixed algorithm fleet who want one place to point hardware and one fee line to reconcile. It does not suit a single rig, because a 0.2 percent fee on one machine buys a dependency you can remove by pointing the miner at the pool directly. Before adopting it, confirm your hardware algorithm appears in the algorithm table, change the shared default panel credentials on first login, and read the install.sh you would be piping into bash, since the documented install path is a curl to bash line with no signature check.

Frequently asked questions

Official sources

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