
Ergo uses Autolykos v2, an ASIC-resistant proof-of-work algorithm built for memory-hard mining. Choosing an Ergo mining pool means comparing fees, payout thresholds, reward methods, and server regions. This guide explains those criteria and shows how to connect a GPU rig.
Autolykos v2 depends on GPU memory and available VRAM as well as compute performance. Memory type, miner version, clocks, power limits, and cooling can all change a card’s result.
The algorithm uses a table whose size increases over time. A card may run the miner but lack enough free memory to prebuild another dataset. That can reduce performance or disable prebuilding. Check current miner documentation before buying an older card with limited VRAM.
ASIC resistance does not make every GPU equally profitable. Test the card with the intended miner and leave memory headroom for the operating system. The pool should also provide regional Stratum servers and worker statistics that expose rejected shares.
Autolykos v2 rewards memory bandwidth and adequate VRAM, while its growing table makes old memory requirements unreliable.
A payout scheme controls when a pool credits submitted shares and who absorbs short-term block variance. It does not change the network reward. Compare the scheme with the fee, payout threshold, and pool size.
A small rig may prefer PPLNS or PPS+ because shared mining reduces payment variance. Solo mining suits an operator willing to accept an uncertain wait between rewards.
PPS+ reduces block-luck variance, PPLNS shares found blocks across a window, and solo leaves the block-finding risk with one miner.
Compare pools by reward method, fee, threshold, regional endpoints, and monitoring. The figures below were checked against the linked pool pages on September 29, 2026. Verify them again before changing a production rig.
| Pool | Published fee | Minimum payout | Reward options | Server information |
|---|---|---|---|---|
| 2Miners | 1% | 1 ERG | PPLNS; separate SOLO pool | Europe, US, Asia |
| Kryptex | 1% for PPS+ and SOLO | 1 ERG | PPS+, SOLO | Global and regional endpoints |
| WoolyPooly | Verify on dashboard | Verify on dashboard | PPLNS, SOLO | Verify current regional endpoints |
| HeroMiners | Verify on dashboard | Verify on dashboard | Pool and SOLO options | Verify current regional endpoints |
This article does not freeze WoolyPooly or HeroMiners figures because their live terms should be checked at connection time. A lower fee can lose its advantage if a distant endpoint produces more stale or rejected shares.
A low threshold matters to a small rig because less ERG remains on the pool. Review live network and coin data, then use the pool directory to compare the available routes.
An Ergo mining pool connects through Stratum. A plain endpoint may use stratum+tcp://HOST:PORT, while an encrypted endpoint may use stratum+ssl://. Follow the pool and miner documentation because supported schemes differ.
Current examples include:
| Region and pool | Endpoint |
|---|---|
| 2Miners Europe | erg.2miners.com:8888 |
| 2Miners US | us-erg.2miners.com:8888 |
| 2Miners Asia | asia-erg.2miners.com:8888 |
| Kryptex global | erg.kryptex.network:7021 |
| Kryptex Europe | erg-eu.kryptex.network:7021 |
Pools also differ on login syntax. One may expect WALLET.WORKER, while another may use WALLET/WORKER. Kryptex documents solo:WALLET for SOLO mode. Copy the example beside the selected endpoint.
Choose the lowest stable latency rather than relying only on a region label. Test failover endpoints before leaving the rig unattended. See how a pool URL and port work before saving the configuration.
A working setup needs a self-custody wallet, compatible mining software, the correct endpoint, and an identifiable worker. Complete the steps in order so each failure has fewer possible causes.
If shares fail, check the wallet, algorithm, endpoint, firewall, and system clock. A missing worker name may not prevent crediting, but it makes troubleshooting harder.
Miner flags differ even when programs connect to the same endpoint. Replace POOL:PORT, WALLET, and RIG01. Then apply the login format required by the pool.
Rigel uses autolykos2 and supports a separate worker argument:
rigel.exe -a autolykos2 -o stratum+tcp://POOL:PORT -u WALLET -w RIG01
lolMiner uses AUTOLYKOS2:
lolMiner.exe --algo AUTOLYKOS2 --pool POOL:PORT --user WALLET.RIG01
SRBMiner-MULTI uses autolykos2:
SRBMiner-MULTI.exe --algorithm autolykos2 --pool POOL:PORT --wallet WALLET.RIG01
BzMiner names the algorithm ergo and accepts a separate worker:
bzminer.exe -a ergo -p stratum+tcp://POOL:PORT -w WALLET --worker RIG01
Run the rig at stock settings until it submits stable shares. Save that baseline before changing clocks, power limits, or intensity.
For rented hashrate, use only an endpoint the pool documents as NiceHash-compatible. A normal GPU endpoint may assign unsuitable share difficulty.
Estimate profitability from measured pool-side hashrate and wall power. A model name alone cannot account for memory vendor, driver, miner build, clocks, cooling, or rejected shares.
| Input | How to measure it | Why it matters |
|---|---|---|
| Pool-side hashrate | Use a representative dashboard average | Reflects credited share performance |
| Wall power | Measure the complete rig at the outlet | Includes the GPU and supporting hardware |
| Rejected-share rate | Read the miner and pool statistics | Rejected work does not earn credit |
| Net ERG credited | Use the selected pool’s records | Captures the pool’s actual reward method |
| Electricity rate | Use the rate charged for the mining period | Converts power use into operating cost |
Software power readings may omit the motherboard, risers, fans, and PSU losses. A wall meter gives a better cost input. Cards near the dataset limit also need unused memory for the operating system and miner.
Use this daily calculation:
daily net = net ERG credited × ERG price − (wall watts ÷ 1,000 × 24 × electricity rate)
Confirm whether a calculator reports gross or net ERG so you do not subtract fees twice. Network difficulty determines how hashrate becomes expected ERG. Use a representative multi-hour average to calculate mining profit before switching pools.
ERG emission limits the supply available to miners. ErgoDocs caps total supply at 97,739,925 ERG. Its published schedule reduces the block reward in steps and then stabilizes it at 3 ERG per block.
Over a long sample, a pool’s expected share of found blocks follows its share of network hashrate. Short samples can differ sharply. That variance explains why a PPLNS dashboard can show favorable or unfavorable luck without proving that the pool changes the network reward.
When the block reward changes, gross ERG per block changes with it. A percentage pool fee still takes the same proportion. Reassess electricity cost, difficulty, transaction revenue, storage-rent revenue, and rejected shares instead of treating past coin output as permanent.
A pool can smooth payment timing, but it cannot remove Ergo’s emission schedule or network difficulty.
Trust a pool only after its worker page, block history, and payout records agree with the miner. Compare local hashrate with a longer pool average because shares arrive unevenly.
Before leaving a rig unattended, verify:
Pool balances are ledger credits, not self-custody. Move completed payouts to a wallet whose recovery phrase you control. If you convert ERG, compare exchange support, deposit policies, withdrawal limits, and fees. Seek qualified guidance for tax treatment in your jurisdiction.
Do not mine directly to an exchange unless it confirms that it accepts deposits from mining pools.
Keep only the unpaid pool balance needed to reach a practical payout threshold.
Choose one pool, test it with a single rig, and confirm a complete payout before moving the rest of your GPUs.
Solo mining credits a block reward only when your worker finds a block. PPLNS and PPS+ spread rewards or share credits across participating miners. Operators with limited hashrate usually prefer a shared pool because it reduces payment variance.
Pool luck compares found blocks with the statistical expectation for the pool’s hashrate. An orphaned block did not enter the accepted chain, so the pool cannot distribute its expected reward. Evaluate both metrics over a meaningful sample.
The Autolykos table grows over time, so old minimum-VRAM figures can become unreliable. Check the current miner documentation and leave memory headroom for the operating system. Test the exact card and miner before buying more hardware.
A pool balance does not give you custody of the private keys. A shutdown, compromise, or account error can delay access. Set a practical payout threshold and move completed payouts to your own Ergo wallet.
The following first-party pages support the technical and numerical claims in this article.