A mining pool Stratum address is the connection detail that tells your miner where to send its hashrate and where to receive mining work. In practical terms, it is the pool server address and port, sometimes shown as a complete URL such as `stratum+tcp://btc.viabtc.io:3333`. You normally enter it alongside a worker name and, depending on the pool, a password or optional setting.

Getting this information right matters. A single wrong character, unsupported protocol, or incorrect worker format can leave a machine offline, create rejected shares, or prevent the pool from associating work with the correct account. This guide explains the parts of a Stratum connection and a reliable way to configure one.

What a Mining Pool Stratum Address Is

Stratum is a mining communication protocol. It lets a mining device or mining proxy connect to an upstream pool service, receive work, and submit results. The pool uses those results to measure each miner’s contribution and apply its payout rules.

A mining pool Stratum address is not a wallet address. It is a network destination for your miner. Think of it as the pool’s work gateway: your machine connects to that gateway, receives jobs to hash, and reports qualifying results called shares.

A complete address commonly includes three technical parts:

A protocol prefix, such as `stratum+tcp://` or a secure variant offered by the pool.

A hostname, such as `btc.viabtc.io`.

A port number, such as `:3333`.

The pool’s official configuration page is the source of truth for these values. Do not assume that a host or port used for one coin, algorithm, or region will work for another.

How to Read a Stratum Address

Protocol, host, and port

Consider this illustrative format: `stratum+tcp://btc.viabtc.io:3333`

The `stratum+tcp://` portion tells compatible software which connection method to use. Some miner interfaces do not ask for the prefix; they provide separate fields for protocol, URL, and port. Follow the labels in the interface rather than pasting a full URL into a port-only field.

`btc.viabtc.io` is the hostname. It identifies the pool server your miner will contact. Pools may publish multiple hostnames for different regions, coins, algorithms, or connection types.

`3333` is the port. A port directs the connection to a specific service on the server. A pool may offer several ports, sometimes to support different connection methods or hashrate ranges. Use only a port documented for your exact setup.

Worker name and password

The Stratum address is only one part of configuration. Your miner also needs a worker identity. The required format differs by pool. Common formats include:

An account name followed by a worker label, such as `account.worker1`.

A wallet address followed by an optional worker label.

An account or subaccount identifier supplied by the pool dashboard.

The worker label helps you distinguish devices. Names such as `garage-s19`, `rack-a-01`, or `gpu-rig-2` make it easier to identify a failed or underperforming machine later.

The password field may be a pool account password, a simple placeholder, or an optional parameter field. It is not safe to guess. Use the pool’s official instructions. If the pool says to use a placeholder, do not substitute a sensitive password unless its documentation specifically requires one.

How a Miner Uses the Connection

Once the miner reaches the pool server, it establishes a mining session. In Stratum V2 terminology, mining devices open channels with upstream Stratum nodes, which can be pools or proxies. The upstream side can assign work and receive share submissions for that session.

The pool sends a job: a defined range of work related to a candidate block. Your hardware hashes that work repeatedly. When it finds a result meeting the pool’s share target, it sends the share back through the Stratum connection.

An accepted share does not mean your device mined a full block. It means the pool accepted evidence that your miner completed valid work at the assigned difficulty. Pools use their own payout methods and accounting rules to turn eligible contribution into rewards. Read those rules separately before choosing a pool.

If the pool sends new work, the miner should switch promptly. This is normal because the underlying network state can change. A healthy mining dashboard generally shows an active worker, hashrate after an initial reporting period, and accepted-share activity.

How to Configure a Mining Pool Connection

Before you begin

Collect the current details from the official setup page for the coin and algorithm you intend to mine. You need:

• The exact pool URL or hostname.
• The exact port and connection type.
• The expected worker-name format.
• The expected password value or parameter format.
• A payout account or wallet arrangement that matches the pool’s requirements.

Also confirm that your hardware supports the coin’s algorithm. A valid Stratum address cannot make incompatible hardware mine a different algorithm.

Configuration steps

1. Open your miner’s web interface, mining application, or farm-management panel.
2. Find the pool configuration section. Many devices offer primary, secondary, and tertiary pool fields. The extra fields can be used as failover connections if your primary endpoint is unavailable.
3. Copy the official Stratum address exactly. If the interface separates host and port, split the official value carefully. For example, enter the hostname in the URL or server field and the digits after the colon in the port field.
4. Enter the worker identity in the username, worker, or user field. Follow the pool’s punctuation and case requirements. If your pool uses an account name plus worker label, confirm both portions are present.
5. Enter the password or placeholder only as instructed by that pool. Do not expose account passwords in screenshots, shared configuration files, or untrusted management tools.
6. Save and apply the configuration. A device may restart its mining process or briefly reconnect.
7. Check the local miner log first. Look for successful connection, authorization, job receipt, and accepted-share messages. Then check the pool dashboard after its normal reporting delay.

When setting up a ViaBTC account or any other pool, copy connection details from that pool’s current official mining guide rather than reusing an old configuration from a forum, video, or another coin.

Choosing the Right Server and Port

Region and latency

Many pools provide more than one server location. Choose the recommended server closest to your operation when the pool provides regional choices. Lower network delay can help the miner receive new work quickly and submit shares promptly.

Location is not the only consideration. Availability, connection stability, and the pool’s current instructions all matter. If you operate machines in more than one region, test each location with its own appropriate endpoint rather than assuming one server is best everywhere.

Protocol and firmware compatibility

Not every miner and firmware version supports every Stratum variant or encrypted connection option. Stratum V2 is a defined successor to Stratum V1, but a pool’s published endpoint must still match what your device supports.

Use a standard endpoint only when your hardware and the pool documentation indicate compatibility. If a pool offers a TLS or secure connection option, confirm that your firmware supports it before selecting it. Changing a protocol prefix without changing the rest of the configuration is not a reliable upgrade path.

Troubleshooting Stratum Connection Problems

If a mining pool Stratum address does not work, troubleshoot in a fixed order instead of changing several settings at once.

Connection errors

Start by checking for typing errors in the hostname and port. Then confirm that the selected address belongs to the correct coin and algorithm. An address for a Bitcoin SHA-256 pool is not interchangeable with an endpoint for another algorithm.

Next, verify that your network permits the outbound connection. Router rules, firewall policies, DNS failures, or restricted networks can prevent a miner from reaching a pool. If the device supports multiple pool entries, configure a documented backup endpoint to preserve continuity during a server or network issue.

Rejected shares and missing workers

A small number of rejected shares can occur, but a persistent high rejection rate deserves attention. Check the miner log for stale-work messages, network interruptions, clock problems, overheating, unstable overclocks, or firmware warnings. High latency can also contribute when work changes quickly.

If the device appears connected locally but not in the pool dashboard, confirm the worker-name format and allow the pool’s normal reporting interval. Check that the username is linked to the intended account or wallet arrangement. Never paste a private key or recovery phrase into a miner worker field; a legitimate pool configuration does not require it.

A Safe Final Checklist

Before leaving a miner unattended, verify the following:

• The Stratum host, port, and protocol came from the pool’s current official guide.
• The selected endpoint matches the intended coin and hardware algorithm.
• The worker name follows the required account or wallet format.
• The dashboard shows the expected worker after the normal reporting delay.
• The miner log shows accepted shares and no recurring authorization or connection errors.
• Backup pool entries are current and intentional.

A correct Stratum configuration is simple once each field has a clear purpose. Treat the pool endpoint as live operational information, verify it before use, and keep device labels organized so problems can be isolated quickly.