TCMINERPROXY SERVER + TMS LOCAL CLIENT
MinerProxy Mining Pool Proxy Software for Mining Farms
TCMinerProxy manages miner connections, proxy ports, upstream pools, wallet policies, statistics, and security on the server, including hashrate routing, pool forwarding, and its unique lossless fee mode. TMS runs at the mining site, aggregating local miners into an encrypted compressed link to TCMinerProxy.
ONE PRODUCT FAMILY, TWO APPLICATIONS
Clear responsibilities, complete collaboration
TCMinerProxy owns server-side policy and operations. TMS owns local access and network optimization. Use either access path according to the needs of each site.
TCMinerProxy
A server management system for miners, mining sites, and pool operators, covering proxies, policy, observability, security, and expansion.
- Create and manage mining pool proxy, relay, and forwarding ports
- Configure upstream pools, wallets, worker names, and fee policies
- Inspect hashrate, devices, latency, connections, and runtime logs
- Extend into a self-owned pool with PoolNode settlement features
TMS Client
A secure on-site client with the new TMS3 (NB) protocol for substantially stronger compression of BTC and LTC pool traffic.
- Give local miners a consistent LAN connection address
- TMS3 (NB) covers every BTC and LTC pool and reduces public traffic volume by up to 95%
- Reduce public data volume and consolidate outbound connections
- Monitor ports, links, traffic, CPU, and memory
TWO ACCESS PATHS
Choose by site scale and network conditions
TMS is an optional local access client for TCMinerProxy. Miners can connect directly in simpler environments, or use TMS when the site has more machines or a constrained public link.
Miners connect directly to TCMinerProxy
A shorter, simpler path for sites with fewer miners, stable networking, and sufficient bandwidth.
Miners use TCP/SSL to reach TCMinerProxy, which manages the upstream pool connection.
Miners connect to local TMS first
TMS aggregates connections on the LAN and reaches TCMinerProxy through an encrypted compressed link; TMS3 (NB) can further cut public traffic for BTC and LTC pools.
Designed for larger fleets, costly bandwidth, limited public connections, or unified multi-site access.
TMS does not replace TCMinerProxy. Proxy ports, pool targets, wallet policies, statistics, and security remain the responsibility of the TCMinerProxy server.
Up to 95% less public traffic across every BTC and LTC pool
TMS3 (NB) efficiently compresses connections across the full range of BTC and LTC pools while preserving pool compatibility. TMS continues to handle local access, encrypted links, connection consolidation, and on-site monitoring.
Unified local access
Miners use LAN addresses, so remote route changes do not require editing every miner.
TMS3 (NB) all-pool compression
Supports every BTC and LTC pool and reduces public-network traffic volume by up to 95%.
Connection consolidation
Compress a large number of incoming miner links into fewer public outbound connections.
Multi-address load balancing
One local port can use multiple compatible TCMinerProxy remote addresses.
On-site monitoring
Inspect incoming and outgoing connections, network traffic, CPU, memory, and port state.
Manage miners, policies, and pool connections on the server
Whether miners connect directly or through TMS, TCMinerProxy remains the management core for the complete path from proxy configuration to runtime observability.
- Third-party mining pool proxy, relay, and forwarding
- Wallet, worker-name, and fee policy management
- Live hashrate, devices, latency, and connection logs
- Security controls, configuration backup, and multi-instance control
- Self-owned pool capabilities through PoolNode
DEPLOYMENT SCENARIOS
From one mining site to multi-region operations
Direct and TMS-enhanced access can be mixed by site, so every location does not have to use the same deployment model.
Small mining site
Use TCMinerProxy for mining pool proxy, relay, and unified monitoring when the miner count is modest and the network is stable.
Miners → TCMinerProxy → Third-party poolLarge mining site
Run TMS locally to aggregate a large miner fleet and reduce pressure on public connections and bandwidth.
Miners → TMS → TCMinerProxy → PoolMulti-site operations
Deploy TMS at each site and connect them to one or more centrally operated TCMinerProxy servers.
Site TMS clients → Central serverSelf-owned pool
Combine TCMinerProxy with PoolNode for a pool website, user queries, and settlement-layer capabilities.
TCMinerProxy → PoolNode real poolPRODUCT RELATIONSHIP
Common questions about TMS
Is TMS required to use TCMinerProxy?
No. TMS is an optional local access client. Miners can also connect directly to TCMinerProxy over TCP/SSL.
Can TMS replace TCMinerProxy by itself?
No. TMS handles local access, connection consolidation, and link optimization. Proxy policy, pool targets, statistics, and security remain on the TCMinerProxy server.
When should I deploy TMS?
TMS is recommended when a site has many miners, limited public connections, expensive bandwidth, or a need to manage local miner access addresses centrally.
Connect to leading pools—or build your own
TCMinerProxy is honored to be supported by these and more partners.
- Third-party pools · Direct access
- PoolNode · Self-owned pool expansion
START DEPLOYING
Choose the access path that fits your site
Deploy TCMinerProxy directly, or pair it with TMS for a complete local-access and server-management path.
- Stable network / standard siteDeploy TCMinerProxy directly
- Many miners / constrained bandwidthPair with the TMS client




