RustMinerSystem

RustMinerSystem server + RMS local client

Local miner access. Centralized server control.

RustMinerSystem 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. RMS runs at the mining site, aggregating local miners into an encrypted compressed link to RustMinerSystem.

One product family, two applications

Clear responsibilities, complete collaboration

RustMinerSystem owns server-side policy and operations. RMS owns local access and network optimization. Use either access path according to the needs of each site.

Server core

RustMinerSystem

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
Local client

RMS Client

A secure on-site client with the new RMS3 (NB) protocol for substantially stronger compression of BTC and LTC pool traffic.

  • Give local miners a consistent LAN connection address
  • RMS3 (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

RMS is an optional local access client for RustMinerSystem. Miners can connect directly in simpler environments, or use RMS when the site has more machines or a constrained public link.

Direct access

Miners connect directly to RustMinerSystem

A shorter, simpler path for sites with fewer miners, stable networking, and sufficient bandwidth.

Miners use TCP/SSL to reach RustMinerSystem, which manages the upstream pool connection.

RMS-enhanced access

Miners connect to local RMS first

RMS aggregates connections on the LAN and reaches RustMinerSystem through an encrypted compressed link; RMS3 (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.

RMS does not replace RustMinerSystem. Proxy ports, pool targets, wallet policies, statistics, and security remain the responsibility of the RustMinerSystem server.

RMS client · RMS3 (NB)

Up to 95% less public traffic across every BTC and LTC pool

RMS3 (NB) efficiently compresses connections across the full range of BTC and LTC pools while preserving pool compatibility. RMS continues to handle local access, encrypted links, connection consolidation, and on-site monitoring.

Available protocolsRMS2RMS3RMS3 (Zstd) RMS3 (NB) UP TO 95%

Unified local access

Miners use LAN addresses, so remote route changes do not require editing every miner.

RMS3 (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 RustMinerSystem remote addresses.

On-site monitoring

Inspect incoming and outgoing connections, network traffic, CPU, memory, and port state.

RustMinerSystem

Manage miners, policies, and pool connections on the server

Whether miners connect directly or through RMS, RustMinerSystem 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 RMS-enhanced access can be mixed by site, so every location does not have to use the same deployment model.

01

Small mining site

Use RustMinerSystem for mining pool proxy, relay, and unified monitoring when the miner count is modest and the network is stable.

Miners → RustMinerSystem → Third-party pool
02

Large mining site

Run RMS locally to aggregate a large miner fleet and reduce pressure on public connections and bandwidth.

Miners → RMS → RustMinerSystem → Pool
03

Multi-site operations

Deploy RMS at each site and connect them to one or more centrally operated RustMinerSystem servers.

Site RMS clients → Central server
04

Self-owned pool

Combine RustMinerSystem with PoolNode for a pool website, user queries, and settlement-layer capabilities.

RustMinerSystem → PoolNode real pool

Product relationship

Common questions about RMS

Is RMS required to use RustMinerSystem?

No. RMS is an optional local access client. Miners can also connect directly to RustMinerSystem over TCP/SSL.

Can RMS replace RustMinerSystem by itself?

No. RMS handles local access, connection consolidation, and link optimization. Proxy policy, pool targets, statistics, and security remain on the RustMinerSystem server.

When should I deploy RMS?

RMS is recommended when a site has many miners, limited public connections, expensive bandwidth, or a need to manage local miner access addresses centrally.

RustMinerSystem is honored to be supported by these and more partners.

Start deploying

Choose the access path that fits your site

Deploy RustMinerSystem directly, or pair it with RMS for a complete local-access and server-management path.