Documentation
TMS Secure Mining Link Documentation
Configure TMS secure mining links, TMS2 and TMS3 protocols, port mapping, encrypted traffic compression, monitoring, capacity testing, and rollback.
TMS Documentation
TMS is the optional secure local client in the TCMinerProxy ecosystem. It is usually deployed inside the mining-site LAN. Miners connect to local TMS first, and TMS connects to TCMinerProxy server ports through TMS2, TMS3, or TMS3(Zstd), reducing public connection count, compressing traffic, and keeping miner traffic on a controlled path.
For TCMinerProxy server installation, backend security, and regular proxy-port configuration, read the TCMinerProxy documentation. This collection focuses on the TMS local client and TMS protocol-port boundaries.
When To Use TMS
- Many miners share one site and you want fewer public outbound connections.
- Public bandwidth is expensive and traffic compression matters.
- Miners should connect only to local LAN addresses.
- You want to use TMS3 or TMS3(Zstd) high-compression paths.
- You need local visibility into inbound connections, outbound connections, disconnect logs, and resource usage.
If the site has only a few miners, stable network, and enough bandwidth, miners can also connect directly to TCMinerProxy proxy ports without TMS.
Access Topology
Miner -> Local TMS -> TMS2/TMS3/TMS3(Zstd) encrypted compression link -> TCMinerProxy proxy port -> Upstream pool
TMS does not replace the TCMinerProxy server. The server still owns proxy ports, target pools, fee wallets, statistics, security, and operations. TMS owns local miner access and compressed transmission to the server.
Feature Chapters
| Chapter | Use it for |
|---|---|
| Installation | Install TMS3 on Linux and Windows, choose architecture, and understand default access after installation. |
| Setup and pairing | First launch, push URL, skip mode, server prerequisites, and pairing workflow. |
| Port mapping | Create local listening ports, bind remote TMS addresses, configure coin, protocol, password, and load balancing. |
| Compression settings | Choose TMS2/TMS3/TMS3(Zstd), set super compression, compression level, and connection-compression count. |
| Monitoring and operations | Read CPU, memory, network, connection charts, port status, filters, and security settings. |
| Troubleshooting | Diagnose miner access, server pairing, high rejects, port conflicts, safe-route mistakes, and rollback. |
Protocol Choices
| Protocol | Description |
|---|---|
| TMS2 | TMS compression TLS protocol. It reduces public connection count and compresses part of the data volume. |
| TMS3 | Group compression protocol with higher compression ratio and higher CPU pressure. |
| TMS3(Zstd) | TMS3 variant based on Zstd. It usually has lower CPU pressure than TMS3 with similar connection behavior. |
When using TMS3 or TMS3(Zstd), the server port, local TMS port, coin, password, super compression, and compression level must match. Mismatched settings can prevent miners from connecting, increase rejects, or break statistics.
Rollout Outline
- Create a test TMS protocol port on the TCMinerProxy server.
- Add a matching local TMS port.
- Connect 1 to 5 test miners.
- Watch TMS inbound/outbound connections, server port status, upstream workers, and reject rate.
- Adjust compression level, super compression, and connection-compression count.
- Increase miner count gradually.
- Back up TMS client configuration and TCMinerProxy port configuration after the target scale is stable.
TMS3 is sensitive to CPU. If small coins or special miners behave abnormally, first lower compression level or disable super compression for testing.