🎯 On pool.kryptex.com, vardiff is on by default — the pool automatically picks the right share difficulty for each worker.
🛠 For SHA256, Scrypt, RandomX, kHeavyHash (KAS), and Ethash (ETC, ETHW, OCTA), you can also set a fixed difficulty manually through the worker password.

👉 Mining pool share difficulty

How vardiff works

Vardiff (variable difficulty) lets the pool set the share difficulty for each worker automatically. It watches how fast your shares come in and tunes the difficulty so a worker submits roughly one share every 60 seconds.

What this means in practice:

• Any hardware connects without setup — from a single CPU to industrial ASICs.
• If hashrate shifts (cards heat up, firmware glitches, a worker drops offline), vardiff retunes right away.
• The pool isn't flooded with tiny shares, and it balances the load evenly.

Vardiff is enabled by default for every algorithm on Kryptex Pool.

Static difficulty vs. vardiff

A static difficulty is a fixed value you set in the worker password. The pool then sends shares at exactly that difficulty and stops adjusting it.

Common reasons to use it:

• Measuring hashrate precisely from pool stats.
• Running stratum proxies or custom setups that need a predictable difficulty.
• Debugging a miner or ASIC firmware.

If the value you set turns out too low or too high, the pool falls back to vardiff automatically — a bad number won't break anything.

Setting a custom difficulty

Supported algorithms: SHA256, Scrypt, RandomX, kHeavyHash (KAS), Ethash (ETC, ETHW, OCTA).

In the worker password, specify d=<number> — for example, d=2147483648.

The formula

D = (hashrate × time) ÷ const

• hashrate — the device's hashrate in H/s (not TH/s or GH/s).
• time — the target time per share, in seconds. Use 60 — it's the sweet spot between pool load and stat accuracy.
• const — the algorithm constant:

Algorithm	const
SHA256	2³² = 4,294,967,296
kHeavyHash	2³² = 4,294,967,296
Scrypt	2¹⁶ = 65,536
RandomX	1 (D = hashrate × time)
Ethash	1 (D = hashrate × time)

Worked examples

SHA256, 200 TH/s ASIC:

• hashrate = 200,000,000,000,000 H/s
• D = (200,000,000,000,000 × 60) ÷ 4,294,967,296 ≈ 2,793,968
• Password: d=2793968

Scrypt, 9 GH/s ASIC:

• hashrate = 9,000,000,000 H/s
• D = (9,000,000,000 × 60) ÷ 65,536 ≈ 8,240,723
• Password: d=8240723

RandomX, 3 KH/s CPU:

• hashrate = 3,000 H/s
• D = 3,000 × 60 = 180,000
• Password: d=180000

✅ Why vardiff is the better default

The pool sees your worker's actual speed, not a number from a spec sheet. That makes it better at picking the right difficulty than any manual calculation — real performance always drifts, and vardiff accounts for that on its own.

Set the difficulty by hand only when you have a specific reason — measurements, a stratum proxy, or debugging. In every other case, vardiff does a better job.

❌ Share difficulty doesn't affect your earnings

A common misconception: "If I raise the difficulty, I'll earn more." That's not how it works.

• PPS and PPLNS weigh every share by its difficulty — a big share is worth more, a small one less. So your hashrate × time stays the same at any difficulty. With fewer shares, each is worth more; with more shares, each is worth less. The total payout is identical.
• In solo mining, share difficulty doesn't matter at all. Your chance of finding a block depends on your hashrate vs the network difficulty. How the pool tracks your shares has nothing to do with it.
• Luck — meaning payout variance on PPLNS — depends on round length and pool behavior, not share difficulty.

Share difficulty only changes how finely the pool tracks your work and how much network traffic it generates. It doesn't change what you earn.

Need Help?

Have any questions, something unclear, or trouble connecting?

Contact support — we're happy to assist!

• Support Ticket.
• Telegram Support.
• Discord Support.
• Email support at support@kryptex.com.