XBT pool settings for rented Blake2b hashrate: URL, worker, password

By the TideHash team · 18 October 2026 · 6 min read

Most rental problems come down to three fields: pool URL, username and password. Get them right and hashrate shows up on your pool within minutes. This guide covers what to put in each field for public XBT pools and for your own gateway, plus how to troubleshoot when nothing appears.

The three fields that matter

On TideHash you leave out stratum+tcp:// because it is added automatically. Everything else should match your pool's start page character for character.

Pool URL: get the port right

Pools often publish several ports, and picking the wrong one is the most common mistake.

• Hardware or difficulty ports. Some pools split ports by starting share difficulty. B2Pool, for example, lists one port for ASICs, others for GPU and CPU, and a separate one for solo mining. Rented Blake2b hashrate comes from ASICs, so use the ASIC or high-difficulty port.
• Solo ports. A solo port means only blocks found by your own hashrate pay you. If that's not what you want, don't pick it by accident.
• Gateway-only ports. Ports a DATUM gateway uses to talk to the pool are not for miners. DxPool states that its gateway port 28915 can't take miner connections directly. Riptide works the same way: its DATUM ports, such as riptide.maveth.ca:29120, are where your gateway connects, so rented hashrate goes to your gateway first.
• Node RPC ports (typically 8332) are never a stratum address.

Pool user: address and worker name

Most XBT pools use your payout address as the account, so there's no signup. Add a dot and a short worker name to tell the rental apart from other machines:

bc1q…example.rig01

• Use an address from a wallet for the XBT chain. It looks the same as a BTC address, so double-check you copied the right one.
• Keep worker names simple: lowercase letters and digits. DxPool, for example, accepts only digits and lowercase letters, up to 64 characters.
• Some pools don't take sub-accounts in the username, only an address. Others use an account name, often written youraccount::rig01 on DATUM gateways. Follow the pool's own instructions.
• TideHash's "Look up your rental" uses the address part of this field, so use the same address you will look up.

Password

Most Blake2b pools ignore the password, so x is fine. Some pools let you request a starting difficulty here. B2Pool, for example, accepts d=8192. Only use this if your pool documents it. Vardiff (automatic difficulty) normally settles within a minute or two anyway.

Sending hashrate to your own DATUM / RATUM gateway

Running your own gateway means your own node builds the block templates. If you want rented hashrate to go there, note the following:

1. Your node must be on the XBT chain. Pool guides currently ask for Bitcoin Knots 29.4.2 or later. DxPool also notes that XBT needs the RATUM gateway, because the original datum_gateway doesn't support XBT.
2. Use the gateway's stratum listen port as the pool URL, often 23334. Don't use the gateway's pool connection or its admin page port.
3. Point the gateway at your pool. For Riptide that is riptide.maveth.ca:29120 (0% fee), as listed on Riptide's How to connect page. This goes in the gateway config, not in the TideHash order form.
4. It must be reachable from the internet. Rented hashrate arrives from outside your network, so the stratum port needs a public IP or hostname and an open firewall rule. Keep the admin and RPC ports closed.
5. Check the username rules of your gateway. Some gateway setups pay the address set in the gateway config and expect only a machine name in the username. Lazarus Pool's gateway notes explain this case. If yours works that way, enter a plain worker name.
6. Add a public pool as backup (next section) so a home internet outage doesn't strand your order.

Use a backup pool

On TideHash you can click + Add backup pool and enter a second host, user and password. It is used only if your main pool can't be reached. While it mines to the backup, your order keeps running and counts as delivered, and it switches back once the main pool works again. A good backup is a different pool, or at least a different server, from your main one.

Test before you pay

A one-minute check from any computer can save an order:

# does the port answer?
nc -vz your-gateway-ip 23334

If it says "succeeded" or "open", the host and port are reachable. Also open your pool's dashboard with your address. Many pools show a page even before the first share arrives.

Troubleshooting: nothing shows up on my pool

Changing pools on a running order

You can switch the destination of a running order from your private order link, or from "Look up your rental" after confirming by email. The new pool is tested before the switch, so a typo won't take your hashrate offline. Your remaining paid time carries over.

One more thing: algorithms don't mix

Blake2b hashrate only works on Blake2b pools, and SHA-256 hashrate only on SHA-256 pools. You can't point TideHash hashrate at a BTC pool, or Bitcoin miners at an XBT pool. To learn more about the coin itself, read What is XBT?. For the full ordering walkthrough, see How to rent Blake2b hashrate.

Ready to try it? Rent Blake2b hashrate from 1 TH/s, or check the Blake2b hashrate price today. Questions? Ask in our Discord.