Skip to main content
Mining on a pool combines your hashrate with other miners’. Instead of waiting to find a block on your own, the pool finds blocks together and shares the rewards among its miners, which makes earnings regular and predictable. To keep the whole block reward for yourself instead, see Solo Mining.

​
Step-by-step Guide

1

Choose a pool

Parallax pools are listed on miningpoolstats. These take your Parallax address as the user name (checked in October 2026):rplant’s regions are eu, na, asia and ru; coolpool also has eu., us. and asia. hosts. gtpool.io takes its own account ID instead of an address. Hashwarp’s first-run wizard offers these pools too.
Prefer a pool that finds less than half of the network’s blocks. A pool with the majority can reverse payments and block transactions, which puts the coin you mine at risk. The Parallax status page shows each pool’s share, and Hashwarp warns you when your pool has the majority.
2

Start Hashwarp

Replace <POOL_HOST>:<PORT> with the pool’s address and <YOUR_ADDRESS> with your Parallax address.
  • Add --tls for a TLS port.
  • The worker name (rig1) tells your rigs apart on the pool’s dashboard.
  • No password is required for most pools.
Or run hashwarp without options and answer the wizard’s questions: see Configuration.
3

Check that shares are accepted

Each share the pool accepts is logged:
The line shows the GPU that found it, the share’s difficulty, the time the pool took to answer and the shares so far. A rejected share is a warning with the pool’s reason.
4

Check the pool's dashboard

Most pools have a web dashboard where you enter your address to see your hashrate as the pool sees it, accepted shares, pending rewards and payouts. It can take a few minutes to show a new rig.

​
Options

See all options for the timeouts.

​
Failover pools

Hashwarp mines on the first pool and moves to the next when the first fails --pool-retries times in a row. With --failover-timeout 30 it tries the first pool again after 30 minutes on another.

​
Pool URLs

Pools can also be given as URLs, which is how ethminer and Hashwarp 1.x took them (-P still works):
The scheme is stratum, stratum1 (EthProxy), stratum2 (EthereumStratum/1.0.0) or stratum3 (EthereumStratum/2.0.0), followed by +tcp, or +ssl / +tls for TLS. If the URL has no wallet, --wallet and --worker are added.

​
Stratum flavours

Pools speak one of several Stratum dialects. By default Hashwarp tries EthereumStratum/1.0.0, then EthProxy, then plain Stratum, and logs the one the pool accepted:
If a pool needs a particular one, --esm sets it: 0 EthProxy, 1 or 2 EthereumStratum/1.0.0 (NiceHash), 3 EthereumStratum/2.0.0. EthereumStratum/2.0.0 is only used with --esm 3.

​
Difficulty

Pool difficulty is counted in units of 232 hashes, like the pools count it: difficulty 1 is a share every 4.29 billion hashes on average. Hashwarp writes difficulties in hashes, so a pool difficulty of 2 is diff 8.59 GH.

​
Pools with the majority

A pool that finds more than half of the blocks can reverse payments and block transactions. Hashwarp reads the pools’ shares of the last 7 days’ blocks from status.parallaxprotocol.org every 10 minutes. When your pool has the majority it says so at startup and then every hour, with the smaller pools to move to:
The dashboard shows it too, and the first-run wizard lists such a pool last.
  • Hashwarp never changes pools by itself: moving is your choice.
  • The request sends nothing about you or your rig, only Hashwarp’s version as the User-Agent. If it fails, Hashwarp carries on mining without a word.
  • It doesn’t run when solo mining, in simulation, --selftest or --oc-tune.
  • --no-pool-check turns it off.

​
Tips & Troubleshooting

  • Rejected shares with a reason like low difficulty: the pool may need another Stratum flavour; try --esm. Wrong results (the F count): lower the GPU’s overclock.
  • Choose a pool with servers close to you: the share latency in the log should stay well under a second.
  • Make sure your address is right: rewards sent to a wrong address can’t be recovered.
  • More in Troubleshooting.