Two targets serve different purposes
Network difficulty is tied to Bitcoin’s consensus block target. Share difficulty is a pool-assigned accounting target that makes it practical to measure workers’ contributions. Pools may assign different share difficulties to workers with different hashrates.
Raising a worker’s share difficulty generally means fewer qualifying submissions for the same amount of hashing, with more weight assigned to each accepted share. It does not make a device physically hash faster, and it does not rewrite the network’s difficulty.
Step-by-step
- Check the label. Determine whether the value came from network data or a worker’s pool connection. Keep the two values in separate records.
- Weight contributions. Compare accepted work using difficulty-aware statistics, not raw counts alone. Check the provider’s definitions for variable-difficulty accounting.
- Review the interval. After a setting change, allow enough observations to avoid interpreting a smaller sample as lost physical hashrate. Check connectivity and rejection reasons too.
Worked example
Illustrative example. At a hypothetical fixed hashrate, changing assigned share difficulty from 1,000 to 2,000 roughly halves the expected share count while doubling each qualifying share’s work weight.
The word ‘expected’ matters: short-term counts vary. The same physical effort can appear as fewer submissions, so the dashboard needs both difficulty and averaging context.
Common mistakes
- Believing lower share difficulty creates more coins.
- Comparing workers by raw share count after different assignments.
- Treating a pool setting as a Bitcoin consensus adjustment.
Questions and answers
Should I force the lowest possible difficulty?
Follow the pool’s supported configuration. Unnecessary submissions can add overhead, and unsupported settings may not improve credit. Diagnose actual accepted-work performance instead.
Apply this to your setup
Log a worker’s assigned share difficulty before and after any change, alongside accepted difficulty-weighted work and the sampling period. Raw counts alone cannot tell you whether contribution improved. If submission count falls after difficulty rises, check the weighted result before treating the event as lost hashrate.
Sources and next steps
Use shares versus blocks and rejection troubleshooting.
How this guide was prepared: AI-generated drafting with the linked technical references and illustrative calculations. It does not report first-hand equipment tests or a named specialist review.