Mining Pool URL and Port: Stratum Address Explained

A mining pool URL and port identify the server and listener that accept a miner’s Stratum connection. If either value is wrong, the miner cannot submit accepted shares. This guide explains the Stratum address format, plain TCP and encrypted endpoints, worker credentials, backup servers, and connection troubleshooting.

What the URL and port do

The pool URL tells your miner which server should receive its connection. The port selects the mining service listening on that server. Both parts must match the connection details published by the pool.

Mining devices exchange jobs and shares through a mining protocol rather than the pool website. A Stratum address points to a mining host and includes the port for the required listener.

After connecting, the miner receives jobs and submits shares. The pool estimates hashrate from those submissions over time. The miner does not send hashrate as a raw measurement.

A pool URL without its required port is like a street address without the apartment number: the miner reaches the host but not the intended service.

Anatomy of a Stratum address

Read stratum+tcp://pool.example.com:3333 from left to right:

• stratum+tcp:// identifies the protocol and transport expected by the miner.
• pool.example.com identifies the pool host.
• : separates the host from the port.
• 3333 identifies the listener that accepts mining connections.

An encrypted endpoint may use stratum+ssl:// or another format chosen by the pool. Some mining software provides a separate SSL or TLS setting. Pool implementations do not use one universal label, so copy the published format exactly.

The complete endpoint includes the port even when software displays it in a separate field. A hostname copied without its port may be unusable. Guessing a familiar port can select the wrong listener or cause a timeout.

A literal IP address can replace a hostname in some configurations. However, a pool-controlled domain lets the operator move the service without asking miners to enter a new IP address. Do not substitute an IP address from a forum unless the pool publishes it.

TCP port vs SSL port

A plain TCP endpoint carries Stratum messages without transport encryption. An SSL/TLS endpoint encrypts the transport. It can also help detect server substitution when the miner validates the certificate and hostname correctly.

A port number does not enable encryption by itself. The pool assigns a service to the port, while the scheme or miner setting controls TLS. Pairing an encrypted connection mode with a plain listener usually fails.

TLS adds work while the connection starts, but a mining connection normally remains open. Encryption cannot protect a miner whose operator enters an attacker-controlled hostname.

Choose an encrypted endpoint from the pool’s instructions. Port 443 does not automatically mean that a mining connection uses TLS.

Typical pool ports

No Stratum port works as a universal default. The current Braiins and ViaBTC instructions show how ports can vary by pool, coin, endpoint, and connection type.

These values belong to the named endpoints. They do not reserve those ports for a coin or algorithm across every pool.

Treat a copied port as configuration data that can change. Confirm it on the pool’s official connection page before applying it to several rigs.

Worker name and password

The URL opens the connection. The worker identity tells the pool which account or wallet should receive credit for submitted shares.

Pools commonly document formats such as wallet_address.worker_name or account.worker_name. Braiins, for example, uses userName.workerName. Follow the selected pool’s format because the fields are not interchangeable across all services.

Give each miner a distinct worker name, such as farmA-s19-01. Separate names make an offline or underperforming device easier to find on the pool dashboard.

The password field does not always protect the pool account. Braiins states that its documented password can contain any value or remain empty. Other pools may use this field for connection options, so do not reuse the Braiins rule elsewhere.

A miner that reaches the server but fails authorization may have an incorrect worker or password format. Check those fields before changing the pool port.

Finding current connection details

Open the pool’s official Connect, Get Started, Mining Guide, or Help page. Select the correct coin, region, and connection type before copying an endpoint.

Do not rely on a search snippet, chat message, forum post, or old video. Hosts and ports can change while copied instructions remain online. HiveOS documentation also tells users to verify that the selected pool server is correct and current.

Compare the full address character by character. A different subdomain matters as much as a different port. The 2Miners pool page can help you identify the relevant pool, but its official connection instructions remain the authority for live settings.

Keep the official setup page with your farm documentation. The mining pool software guide explains why separate pool deployments can expose different endpoints.

Entering the connection details

Enter the endpoint in the miner’s pool or URL field. Include the scheme and :port when the software expects a complete URL. Put the worker identity and password in their own fields.

Save the configuration and inspect the miner log. A successful restart alone does not prove that the pool accepted the connection.

In command-line mining software

Command-line miners usually accept the endpoint through a configuration file or launch argument. Some expect a complete URL. Others expect only host:port.

Use the syntax documented for that miner and version. A command copied from unrelated software can turn a valid endpoint into an invalid argument.

The log should progress through DNS lookup, socket connection, authorization, job receipt, and share submission. The last completed stage helps locate the fault.

In a HiveOS Flight Sheet

A HiveOS Flight Sheet combines the selected coin, wallet, pool, and miner configuration. HiveOS can supply a stored Stratum address, but its documentation tells users to verify that address against the pool website.

Test a new Flight Sheet on one rig before applying it to the farm. Confirm that the miner receives jobs and that the pool dashboard shows the intended worker.

Backup and regional servers

A published backup endpoint gives the miner another connection path when the primary endpoint fails. Configure it before an outage.

An alternate port on the same host can help when a network blocks the primary port. A different hostname can also cover a server or routing failure.

Choose a region by measured network delay rather than its geographic label. Internet routing can make a nearby location slower than a more distant one.

Higher latency leaves less time for a share to reach the pool before a job changes. This can raise the stale-share rate while the miner still reports normal local hashrate. The solo mining setup guide uses the same endpoint and failover concepts.

Fake pool addresses

An attacker-controlled Stratum endpoint can accept a miner’s work while attributing the shares elsewhere. The miner may still look active, so compare its status with the expected worker on the real pool dashboard.

A false endpoint can enter through a modified configuration, copied command, compromised management account, altered DNS, or fake setup guide. Warning signs include a missing worker or an unexpected drop in pool-side hashrate.

TLS helps against interception only when the miner validates the certificate and connects to the intended hostname. It does not make a phishing hostname legitimate. The Stratum V2 specification notes that Stratum V1 lacks cryptographic authentication.

A fake pool URL may leave the wallet untouched while redirecting the rig’s submitted work.

Copy endpoints from the official pool site and verify the domain before saving them. Restrict access to miner profiles and recheck stored URLs after firmware, router, or management-platform changes.

Connection troubleshooting

First separate a connection failure from a rejected share. A wrong or blocked port commonly produces a timeout, refused connection, or repeated disconnect. A rejected share appears only after the miner has connected and submitted work.

Use this order:

1. Compare the scheme, hostname, port, coin, and region with the pool’s official page.
2. Check whether the hostname resolves. A successful ping does not prove that a TCP port is open.
3. Test the listener with Test-NetConnection pool.example.com -Port PORT on Windows or nc -vz pool.example.com PORT where Netcat is available.
4. Review local firewall, router, hosting-provider, and ISP rules if the hostname resolves but the port fails.
5. Read the miner log for connection, authorization, job, accepted-share, and rejected-share events.
6. Try only an alternate port or backup host published by the pool.
7. Confirm that the expected worker appears on the pool dashboard.

If the socket connects but authorization fails, inspect the worker and password fields. If jobs arrive but shares are rejected, check the selected coin, algorithm, miner settings, and stale-share messages.

Do not expect every pool dashboard to update within the same fixed interval. Check the miner log for accepted submissions before using the dashboard’s hashrate estimate.

Final connection checklist

A connection is ready only after the miner and pool both report activity:

• The scheme, hostname, port, coin, and region match the official pool page.
• The worker identity and password follow the pool’s documented format.
• The configured port accepts a direct TCP connection.
• A published backup endpoint is configured.
• The miner log shows jobs and accepted shares.
• The pool dashboard shows the intended worker.

Fix the first failed layer before changing unrelated firmware or hardware settings. Save the verified configuration, then deploy it to the remaining rigs.

Frequently asked questions

Sources

• Bitcoin Mining Setup — Braiins Academy
• Mining Pools Information — ViaBTC
• How to set up your wallet — HiveOS
• Stratum V2 Specification: Motivation — Stratum V2 Project

Читайте также

• Mining Pool Address: Stratum, Worker & Payout Explained