To configure a mining pool address, enter the pool’s server URL, the correct port, and your worker credentials in your miner’s pool settings. The exact values depend on the coin, mining algorithm, pool, and sometimes your location. A single incorrect character can stop the miner from connecting or send credit to the wrong account.

A mining pool address is the connection point your ASIC miner or mining software uses to submit shares. It is not usually a wallet address. Think of it as the destination server for your hashrate, while your worker name tells the pool which account or payout address should receive credit.

What a mining pool address does

Mining pools combine hashrate from many miners. Your device performs hashing work locally and sends proof of that work, called shares, to the pool. The pool records valid shares and calculates rewards under its payout rules.

The mining pool address tells your device where to send those shares. It commonly uses the Stratum mining protocol and may look similar to this: stratum+tcp://btc.viabtc.io:3333

ViaBTC’s official primary Bitcoin mining address is stratum+tcp://btc.viabtc.io:3333, with port 443 available as a backup.

The format normally has three useful parts:

• The protocol, such as `stratum+tcp` or another protocol shown by the pool.
• The server hostname, which identifies the pool’s mining server.
• The port number, which tells the miner which service for a particular coin or algorithm to use.

Why the correct port matters

A pool may publish several ports for the same coin. Some are intended for different miner sizes, network regions, or difficulty settings. Copy the current address and port from the pool’s official setup instructions for the exact asset you plan to mine.

Information to collect before setup

Before changing your miner settings, gather the details in one place. This makes configuration faster and reduces the chance of typing an incomplete URL.

First, confirm the coin and algorithm. A Bitcoin ASIC, for example, cannot be pointed at a pool endpoint for an unrelated algorithm. The selected endpoint must match what your hardware can mine.

Then collect:

• The primary pool URL and port.
• One or two backup pool URLs, if available.
• The required worker-name format.
• The password format, if the pool uses one.
• Whether the pool uses an account, subaccount, or wallet address for reward attribution.

Pre-save checklist

Before saving the configuration, confirm:

• The selected coin and algorithm match your miner.
• The pool endpoint and port are current.
• The worker name uses the required format.
• The payout destination and method are correct.
• Backup pools use the same coin and algorithm.

Prepare your account or payout wallet

Some pools use an account-based model. In that case, your worker name may follow a format such as `account.worker`. Other pools use a wallet-based model, where your wallet address is used in the worker field, sometimes with a worker label after it.

Do not assume the same format works everywhere. Confirm that the payout address and payout method are correct in the pool dashboard before running equipment for an extended period.

How to configure mining pool address settings

The interface differs by manufacturer, but the setup process is broadly similar for most ASIC miners and mining applications.

1. Open the miner configuration page

Connect the miner to your local network and find its local IP address. Sign in to the miner’s web interface using your authorized administrator credentials. Look for a page named Miner Configuration, Pool, Mining, or something similar.

Mining software usually has equivalent settings in a configuration file, command line, or graphical interface. The fields still follow the same logic: server address, worker identifier, and password.

2. Enter the pool URL

Paste the mining pool address into the URL or server field. Include the protocol and port if the pool shows them. Do not add spaces before or after the address.

For example, the field may require a complete value in this pattern: stratum+tcp://btc.viabtc.io:3333

URL syntax can vary by miner firmware. Some interfaces use one combined URL field, while others require the host and port in separate fields. Follow the labels in your miner’s configuration page and enter each value in the format it expects.

If the device offers Pool 1, Pool 2, and Pool 3, place the preferred endpoint in Pool 1. Add backup endpoints to the remaining fields so the miner can fail over if the primary server is unavailable.

3. Enter the worker name and password

In the worker field, enter the identifier required by the pool. Common formats include:

• account.workername
• subaccount.workername
• walletaddress.workername
• A wallet address without a separate worker label

The worker label is usually a name you choose, such as `garage-asic-01` or `rack2-unit4`. Clear labels make it easier to identify a device that is offline, overheating, or underperforming.

The password field may be required even when the pool does not use it for authentication. Some pools accept a simple placeholder, while others use it for optional settings. Follow the required format exactly; do not place an account password in this field unless the pool explicitly instructs you to do so.

4. Save settings and confirm operation

Save or apply the configuration. The miner may restart its mining process, and it can take several minutes before the dashboard shows stable hashrate and accepted shares.

Check the device status page first. It should show a successful connection to the configured pool and no repeated authorization errors. Then check the pool dashboard to confirm that the worker appears and begins reporting hashrate. Pool-side hashrate can lag behind the local miner display because it is calculated from submitted shares over time.

How to read a typical pool address

A mining pool address is easiest to manage when you separate the server field from the identity field.

The server field answers: “Where does this miner send shares?” The worker field answers: “Who should receive credit for those shares?” The password field answers: “Does this pool need a placeholder or a special option?”

Account-based and wallet-based workers

With an account-based pool, create an account, secure it, and set up a worker under that account. Your pool dashboard typically centralizes hashrate, rewards, payout settings, and notifications.

With wallet-based mining, the wallet address may function as the account identifier. This can be simple, but it increases the importance of checking every character. A valid-looking but incorrect address may not be recoverable once rewards are paid.

For either method, record which worker belongs to each physical machine. This is especially useful when you operate multiple miners or separate locations.

Common configuration problems and fixes

If the miner does not start submitting shares, begin with the simplest checks. Avoid repeatedly rebooting the device before reading its status and kernel log, because the error message often identifies the failed field.

Connection and DNS errors

A connection failure may mean the URL, port, network connection, or DNS resolution is wrong. Confirm that the complete pool URL was copied from the pool’s setup page. Check that the miner has a valid local IP address, gateway, and DNS configuration.

If one endpoint fails, test a backup endpoint for the same coin and algorithm. Do not switch to an unfamiliar pool URL solely because it appears in a forum post or chat message.

Invalid worker or unauthorized errors

These messages usually point to a worker-name problem. Check spelling, separators, capitalization rules, subaccount names, and the required wallet format. Also confirm that the worker was created if the pool requires workers to be registered in advance.

If the pool requires a special password value, replace the generic value with the documented one and save the configuration again.

Low hashrate and rejected shares

A successful connection does not guarantee healthy mining. Compare the miner’s reported hashrate with its expected operating range, taking temperature, power limits, and tuning into account. A small number of rejected shares can occur, but a sustained high rejection rate may indicate network latency, unstable hardware, incorrect settings, or an unsuitable endpoint.

Check fan speed, chip temperatures, power supply stability, firmware alerts, and network packet loss. Review the pool dashboard after enough time has passed for share-based averages to become meaningful.

Security and operating checks before mining

Use the pool’s official setup page and your miner manufacturer’s configuration documentation for endpoints, ports, worker formats, and payout instructions. Bookmark legitimate sites instead of relying on search ads, copied screenshots, or links sent through private messages.

Secure both the miner and the pool account. Change default miner credentials, use a strong unique password for the pool account, enable available multi-factor authentication, and restrict access to the miner’s management interface.

During the first hour after setup, monitor the miner’s local hashrate, accepted-share status, and the worker’s appearance in the pool dashboard. Once those align, your mining pool setup is usually operating as intended. Continue to review payout settings, pool notices, and device health regularly, because endpoints and operating conditions can change over time.