Bitcoin mining pool URL list (Stratum endpoints) — what to use in your miner

People search for a bitcoin mining pool URL list because miners need a pool “address” to connect. In practice, this is almost always a Stratum endpoint: a host and port like pool.example.com:3333. This guide explains how pool URLs work, how to pick the right port, and how to avoid common mistakes when configuring a Bitcoin miner or a bitcoin mining crypto miner app. Use these examples when setting up miners or gateways—our team can also configure multi‑port (TCP/SSL) Stratum endpoints for enterprises and large mining farms.

What a Bitcoin mining pool URL means

A pool URL is the Stratum endpoint miners connect to. Pools often publish multiple endpoints: different regions, TCP vs SSL, and different ports tuned for different miner sizes. Your ASIC or mining software connects, authenticates (wallet/username + optional password), and then receives jobs.

Common Stratum URL formats

You’ll commonly see one of these strings in miner setup screens:

stratum+tcp://POOL-DOMAIN:3333
stratum+tcp://POOL-DOMAIN:443
stratum+ssl://POOL-DOMAIN:3443

• stratum+tcp is plain TCP. It’s widely supported and often the default.
• stratum+ssl (sometimes listed as TLS) encrypts the connection.
• Ports like 3333, 443, 25 are pool/operator choices. Some pools offer “nice” ports to work around restrictive networks.

If you’re a pool operator, publish clear endpoints and keep naming simple. For global pools, consider multi-region Stratum gateways.

Wallets, usernames, and worker names

Pools generally require one of these login styles:

• Wallet-based: WALLET_ADDRESS (plus optional .worker)
• Account-based: username.worker (portal account required)

Worker names help you identify which device is submitting shares. Typical formats:

bc1q...youraddress.worker01
username.rackA-antminerS19-01

Example URL list (formats + examples)

This is not an authoritative, always-current list of public pools (endpoints change). Instead, use it as a quick reference for how URLs are written. Always verify a pool URL on the pool’s official website before connecting hashpower.

Example: your own pool endpoints

stratum+tcp://btc.yourpool.com:3333   (default)
stratum+tcp://btc.yourpool.com:4444   (high diff)
stratum+ssl://btc.yourpool.com:3443   (TLS)
stratum+tcp://us-east.btc.yourpool.com:3333
stratum+tcp://eu.btc.yourpool.com:3333

If you’re looking for a pool URL for crypto miner apps, it’s the same: host, port, and credentials. The difference is the UI. ASICs usually show it as Pool 1/2/3; desktop miners show it as “URL” + “Worker” + “Password.”

Troubleshooting & checklist

• Use the right coin/algorithm: Bitcoin is SHA256. BCH and other SHA256d-family coins need the correct pool endpoint/coin configuration.
• Check firewall/NAT: outbound TCP to the pool port must be allowed. On Linux rigs (btc pool linux), verify with nc -vz host port.
• Try a second port: if 3333 is blocked, 443 is sometimes offered (depends on the pool).
• Confirm worker format: some pools require wallet.worker, others just the wallet.
• Watch stale shares: high latency → more stales. Choose the closest region or ask your pool operator about multi-region gateways.

When you should build your own pool

If you need custom payout rules, private access control, your own branding, or you want to keep fees in-house, it’s often better to create bitcoin mining pool infrastructure on your own domain. Open-source options exist, but “free bitcoin mining pool” software still requires secure servers, monitoring, and safe payout controls.

We provide turnkey builds and operations for Bitcoin/SHA256 pools (Yiimp, Miningcore, NOMP) and we can also build a solo mining pool (CKPool) if your goal is private solo mining. If you’re planning the backend, don’t skip node design—start with Bitcoin node setup (Bitcoin Core).