Wielomonetowa farma: najlepsze praktyki

One server and one client can forward many coins at once. Forwarding itself does not parse the payload, so BTC, LTC, KAS, and other stratum coins share the same tunnel. You separate them with ports.

One pool, one listen port

Create a pool row per upstream endpoint (name, coin, host, port). Then create one port mapping per local listen port. Static mapping is the only routing mode: port 3333 might be BTC, port 3334 LTC, port 5555 KAS.

Miner BTC  →  client:3333  →  tunnel  →  stratum.f2pool.com:3333
Miner LTC  →  client:3334  →  tunnel  →  ltc.f2pool.com:3335
Miner KAS  →  client:5555  →  tunnel  →  your-kas-pool:5555

Practical rules

• Do not reuse a listen_port. The API returns 409.
• Use node_scope "specific" when only one site should expose a coin.
• Set sniffing_parser per coin. stratum-v1 for most SHA-256/Scrypt pools, stratum-v1-ethash for Ethash-style, stratum-v2 only when the pool really is V2.
• Leave agg_enabled false unless that pool is stratum2+tcp with authority_pubkey.
• Point each miner at the client IP and the port for its coin. Wallet and worker names are still configured on the miner, as the pool expects.