How to Connect an ASIC to a Mining Pool Step by Step

To connect an ASIC to a mining pool, open its web interface by IP address, enter the pool's stratum URL, a worker name in the subaccount.worker format and any password in the miner configuration, then save and wait for the restart. Within a few minutes the device appears in your dashboard as an active worker. The steps below use RuPool as the example, but the logic is the same for any pool and any ASIC model.

What to prepare first

You need four things. An ASIC powered up and connected to your local network by Ethernet (industrial ASICs normally have no Wi-Fi). A computer or phone on the same network to open the web interface. An account on the pool with at least one subaccount. And a payout wallet, which is set in the subaccount settings.

At RuPool, subaccounts are created in your dashboard under settings (/my/settings/subaccounts/). Each subaccount has its own wallets and its own statistics, and its name becomes the first part of your ASIC login. If you mine for yourself, one subaccount is enough; for several farms or clients, see the article on worker names and subaccounts.

Pick the pool that matches the device's algorithm. Bitcoin ASICs run SHA-256 and connect to the BTC stratum. Litecoin and Dogecoin ASICs run Scrypt and connect to the LTC stratum, with DOGE credited separately through merged mining. The algorithms cannot be mixed: a SHA-256 device cannot hash Scrypt, and vice versa.

Step 1. Find the IP address and log in

Most ASICs get an address from your router via DHCP on first boot. You can find it in the router's client list or with the manufacturer's network scanner (Bitmain's is called IP Reporter; other brands have similar tools). Many models also report their IP when you press the IP Report button on the control board.

Type the address into a browser, for example http://192.168.1.50. A login prompt appears. Default credentials depend on the vendor and firmware: many Bitmain devices use root / root, other brands have their own, listed in the manual or on a sticker. Change the password right after the first login. An ASIC with a default password on a local network is an easy target, and anyone with access to the settings can swap the pool address and take your hashrate.

Step 2. Fill in the pool settings

Find the miner configuration section: Antminer calls it Miner Configuration, other vendors use Pool Settings, Configuration or something similar. You will see three pool blocks with three fields each.

Field	What to enter	RuPool example
URL	Stratum address with protocol and port	stratum+tcp://enter.rupool.pro:3333
Worker (User)	Subaccount, a dot, worker name	myfarm.rig01
Password	Anything; the pool does not check it	x

Ports depend on the algorithm. For BTC (SHA-256) the main TCP port is 3333; for LTC+DOGE (Scrypt) it is 3334. So a Scrypt device uses stratum+tcp://enter.rupool.pro:3334 as its first pool. The enter.rupool.pro address automatically picks the closest stratum; if you want a specific region, use a regional address, covered below.

A worker name may contain Latin letters, digits and underscores. Avoid spaces, Cyrillic and dots inside the worker name itself, since the dot separates the subaccount from the worker. Give each device its own name so the dashboard shows exactly which ASIC dropped or slowed down.

Step 3. Set up backup pools

The three blocks exist for a reason. The ASIC works on the first pool and falls over to the second, then the third, if the connection is lost. Do not leave pools 2 and 3 empty: a one-minute internet outage with no backup becomes downtime, and downtime is lost earnings.

The sensible approach with RuPool is to use the same pool on different ports rather than a third party's pool. For BTC:

1. Pool 1: stratum+tcp://enter.rupool.pro:3333
2. Pool 2: stratum+tcp://enter.rupool.pro:8888, a fallback port in case your ISP filters the main one
3. Pool 3: stratum+tcp://enter.rupool.pro:443 or the SSL option stratum+ssl://enter.rupool.pro:999

For LTC+DOGE the scheme is the same with different ports: 3334 main, 8889, 444 and 26 fallback, SSL on 998. If you add another operator's pool as a backup, remember that while the ASIC is on it, earnings go there, not to your RuPool dashboard.

Three different ports also help with diagnosis: if 3333 does not connect but 443 works, the cause is traffic filtering at your ISP or on your firewall.

Step 4. Choose a stratum region

Distance to the server affects latency, and therefore the share of work accepted in time. RuPool has an automatic address and four regional ones:

• msk2-ru.enter.rupool.pro - Moscow
• nsk-ru.enter.rupool.pro - Novosibirsk
• hel-fi.enter.rupool.pro - Helsinki
• ala-kz.enter.rupool.pro - Almaty

If unsure, start with enter.rupool.pro: it routes the ASIC to the nearest point. A regional address makes sense when you want to pin a location, for example a farm in Siberia that should use Novosibirsk, or a hosting site in Kazakhstan that should use Almaty. Compare regions by ping from the farm and by the rejected-share rate over a day or two.

Step 5. Save and verify

Click Save & Apply or the equivalent. Most firmware restarts the miner, which takes from a few dozen seconds to a couple of minutes. On the status page the pool should show Alive (or similar), and the hashboard table should fill with hashrate values.

Then verify on the pool side. Open your RuPool dashboard: after a few minutes the worker shows up with a hashrate. At first the number jumps around, because the pool estimates hashrate from accepted shares over an interval and short windows are noisy. Look at 1 to 24 hour values. If you want someone to view statistics without access to your settings, create a watcher link, which shows data without a password.

To compare expected earnings with what you see in practice, use the profit calculator. The BTC pool page collects the current addresses and parameters.

Common connection mistakes

• The worker does not appear in the dashboard. Check for typos in the subaccount name and make sure there is exactly one dot between subaccount and worker. Also confirm the subaccount exists in your account.
• The pool shows Dead. Usually a wrong address, port or protocol: stratum+tcp and stratum+ssl are different schemes with different ports. Check that the device has internet: DNS, gateway, no blocking on the router.
• Port does not match the algorithm. A Scrypt ASIC on a BTC port may connect but its shares will not be accepted. Match the port to the coin.
• The same worker name on several devices. The devices may keep hashing, but their statistics get mixed and you cannot see which one dropped.
• Spaces and invisible characters. Copying from a messenger sometimes adds a trailing space. Enter values carefully.
• Empty backup pools. Not an error at launch, but a loss at the first link failure.
• Default password on the ASIC itself. Not a pool issue, but a security one: change it.

If something does not work, RuPool has 24/7 support chat and Telegram @rupoolpro_support. Send a screenshot of the pool settings and miner status (hide the device password) and the error is usually found quickly.

FAQ

Do I need a real password when connecting to the pool?

Most firmware requires the field to be non-empty, but the pool does not check its value, so any character such as x works. Authorization uses the subaccount and worker name.

Can I connect an ASIC without a computer?

Yes. A phone on the same network is enough, since the web interface opens in a mobile browser. You only need the device IP, which you can take from the router's client list.

How many workers can one subaccount have?

For an ordinary farm the number of workers per subaccount is rarely a constraint; if you are connecting a very large fleet, check the details with support first. In practice, give every device its own name and group farms into subaccounts to keep statistics readable.

How soon do earnings start?

Shares are counted as soon as the connection is up, but the dashboard hashrate settles over a few hours. Payouts run once a day automatically if the accumulated amount has reached the threshold you set in settings.

What if my ISP blocks port 3333?

Use the fallback TCP ports (8888, 443, 25 for BTC; 8889, 444, 26 for LTC+DOGE) or the SSL ports 999 and 998. Encrypted traffic often passes without trouble.