Share Difficulty is the difficulty corresponding to the pool’s target for work submissions. Higher difficulty means a lower numerical target and fewer qualifying hashes for the same number of attempts.
Stratum V2 sends maximum_target in SetTarget. The server rejects hashes above this limit. A lower target is stricter; higher Share Difficulty therefore does not mean a higher permitted hash value. [Stratum V2 — SetTarget and mining channels]
At the same hashrate and normalization convention, changing 1024 to 2048 means roughly half the expected submission frequency. Individual intervals remain random; twice the difficulty does not mean every result arrives after exactly twice the time. [Braiins Academy — Worker management and VarDiff]
Braiins distinguishes submission count from normalized work units. At higher assigned difficulty, an accepted submission carries correspondingly greater weight. Fewer messages alone therefore do not prove less contributed work. [Braiins Academy — Pool work accounting]
Changing Share Difficulty alone neither speeds up an ASIC nor changes the network target. For the same number of independent attempts and the same network difficulty, it does not change block-finding probability; it changes which results are reported to the pool. [Braiins Academy — Pool work accounting]
VarDiff adapts difficulty to hashrate to control traffic between miner and pool. Braiins lets miners set a minimum difficulty. A minimum is a lower bound, not a promise that assigned difficulty stays exactly at that value. [Braiins Academy — Worker management and VarDiff]
In Stratum V2, SetTarget applies to jobs received in the future and already received jobs with empty min_ntime. Already received jobs with populated min_ntime retain a stable target. Do not apply the latest setting to every old result without knowing its job. [Stratum V2 — SetTarget and mining channels]
Braiins Solo’s best share display records the highest difficulty of a share found during the session. It differs from the assigned submission threshold. A high record does not improve the next independent hash’s chance and is not accumulated progress toward a block. [Braiins Academy — Best share]
An excessively high minimum can increase hashrate-estimate variance and trigger false alarms even on a working device. Compare difficulty, measurement period, accepted work and connection state when diagnosing; a short period without a share alone does not prove an ASIC fault. [Braiins Academy — Worker management and VarDiff]
For the clearest picture, read this entry together with Mining Share, Mining Target, Hashrate, Mining Pool. The reverse links also lead from Mining Share, Mining Target, Stale Rate.