What is the difference between pool difficulty and network difficulty?

Network difficulty sets how hard it is to find a valid Monero block. Pool difficulty sets how hard it is to submit a “share”—proof to your mining pool that you are doing work. A share can count toward your pool rewards without being good enough to become a block.

Two targets for the same mining work

When you mine, your device repeatedly produces hashes: numbers calculated from possible block data. Each hash is another attempt to meet a target. A harder difficulty means fewer attempts will qualify.

You do not do one kind of calculation for shares and another for blocks. Your pool checks the same mining work against two targets:

• The pool’s share target: Usually much easier to meet. A result that meets it lets the pool measure your contribution.
• The network’s block target: Much harder to meet. A result that meets it can become a Monero block, provided it also follows the network’s other rules.

A valid block found through a pool is therefore also a qualifying share. Most shares, however, are not blocks.

Who sets each difficulty?

Network difficulty comes from Monero’s rules, not from your pool. It adjusts every block, using recent block timing, to keep the average time between blocks near two minutes.

When more computing power joins the network, difficulty generally rises. When computing power leaves, it generally falls. Individual blocks can still arrive much sooner or later than two minutes.

Pool difficulty is set by your pool. Some pools offer fixed settings. Others use variable difficulty, often called vardiff, which automatically adjusts your share difficulty.

Vardiff aims for a manageable rate of share submissions. A faster miner gets harder shares; a slower miner gets easier ones. This helps the pool track work without receiving an unnecessary flood of messages.

Changing your pool difficulty does not change Monero’s network difficulty.

Why harder shares do not automatically pay more

Think of shares as work receipts. An easier receipt arrives more often and represents less work. A harder receipt arrives less often and represents more work.

For example, if your pool doubles your share difficulty while your mining speed stays the same:

• You should submit roughly half as many accepted shares over time.
• Each share represents roughly twice as much work.
• Your expected contribution stays about the same.

A properly designed pool accounts for share difficulty rather than treating every share as equal. Your actual payout also depends on the pool’s payment rules, fees, accepted work, and sometimes its luck finding blocks.

Lowering share difficulty does not make your device more likely to find a network-valid block. It only makes smaller pieces of your work visible to the pool.

What this means for browser mining

Browser mining may produce relatively few hashes per second. If your service uses share difficulty that is too high for your device, you might wait a long time before seeing an accepted share.

That wait does not necessarily mean mining has stopped. Check your reported mining speed and any connection errors. Also check whether shares are being rejected.

A suitable lower difficulty can give you steadier feedback. It does not increase your device’s computing power or guarantee higher earnings. If a browser service converts shares into an internal balance, check its payout rules rather than assuming every share has a fixed XMR value.

The bottom line

Network difficulty controls what qualifies as a block. Pool difficulty controls how often your work gets recorded as shares. More shares alone do not mean more mining power—or more money.