Documentation
MinerProxy Installation and Operations Documentation
Use the TCMinerProxy MinerProxy documentation to install the server, configure mining pool proxy ports, manage hashrate and wallets, secure access, and troubleshoot operations.
TCMinerProxy English dashboard preview: inspect the proxy workspace, port list, hashrate charts, and server resource status at a glance.
This document records the installation, configuration, runtime, and operations workflow for TCMinerProxy. Replace all placeholders with your real deployment values.
Overview
TCMinerProxy can work as a proxy for third-party mining pools, allocating any configured share of connected miner hashrate to specified third-party pool wallets or worker names. It can also use PoolNode to build a real self-owned mining pool, where configured fees are distributed directly at the coin settlement layer. TMS is an optional companion tool for sites that need lower bandwidth usage or fewer public connections: miners can connect to local TMS first, then reach TCMinerProxy through an encrypted compressed link. Without TMS, miners can still connect to TCMinerProxy directly.
Use Cases
- Mining sites need a unified miner access path and controlled hashrate allocation to specified third-party pool wallets.
- Operators need to build a real pool with PoolNode and distribute configured fees at the settlement layer.
- Network environments need optional compression for miner data volume and public connection count.
- Teams need repeatable installation, configuration, and upgrade procedures.
Operating Modes
Third-Party Pool Proxy
Use this mode when connecting miners to third-party pools. TCMinerProxy sits between miners and third-party pools, allocating any configured hashrate share to specified pool addresses, wallets, or worker names. Validate connection stability and allocation targets with test miners before scaling up.
PoolNode Real Pool
Use this mode when operators need to build a real self-owned mining pool. PoolNode provides the pool-node capability, and configured fees are distributed directly at the coin settlement layer. Before deployment, confirm node sync status, network connectivity, settlement configuration, and recovery procedures.
Optional TMS Local Compression Tool
TMS is not required. It runs locally at the mining site and lets miner traffic reach TCMinerProxy through an encrypted compressed link, reducing transmitted data volume and public connection count. Third-party pool proxy mode and PoolNode real-pool mode can both use TMS, but miners can also connect directly to TCMinerProxy without it. Before enabling it, confirm server and client version compatibility and document the rollback plan.
Feature Usage
The new Feature Usage category documents each main backend workflow as its own chapter:
| Feature | Chapter |
|---|---|
| Dashboard and coin monitoring | Dashboard |
| Proxy port creation and editing | Create Proxy Port |
| Port list and batch operations | Port List |
| Per-port workers, wallets, logs, and TCP monitor | Port Detail |
| Fee wallet hot updates | Fee Hot Update |
| Wallet and worker hot replacement | Wallet / Worker Hot Replacement |
| Security, presets, certificates, notifications, and import/export | Settings Center |
| Runtime, security, and troubleshooting logs | Log Manager |
| TMS push address and port mapping | TMS Client |
| Multi-instance fleet monitoring | Remote Control |
| Algorithm and coin engine data | Algorithm Engine |
| Remote APP_INFO and application links | APP Entry |
