<p>It's hardware specific, and most of the information for Bitcoin mining ASIC are under an NDA so this can't be posted publicly. There's very little utility in returning difficulty one shares to the controller, for a device doing 1TH/s it would mean dealing with hundreds of results a second that the controller is just throwing away. </p>

<p>The difficulty of a "share" is whatever the hash target was, if we have a target of difficulty 256, then any valid block header with a difficulty more than this would make that "share" valid for the target. Shares with a vastly higher difficulty (in the billions today) might also be valid as a block for their parent pool. Shares are only used by pools to gauge how much work a client is putting into finding a block (they are simply blocks with too low of a difficulty to be valid), they're completely useless for anything else and thrown away. </p>

CC BY-SA 3.0
2015-04-06T04:51:30.573Z
2015-04-06T04:51:30.573Z
Claris
<p>Are they preset to only return difficulty 1 shares when the find a nonce?  Then mining software verifies if it meets current target difficulty?  Or, if given a different target difficulty, will the ASIC only return shares that meet that difficulty setting?</p>

<p>If this is hardware specific, any idea which chips allow variation in the target difficulty?</p>

<p>The question in part stems from some misunderstandings I have seen on questions of what a share is.  Whether it is always a nonce found for difficulty 1, or if it is a nonce found for the target difficulty sent to the miner.  There are some confusing answers out there.</p>

<asic><difficulty><nonce><mining-pool-shares><miner-configuration>
When ASICs generate a share, is it always at difficulty 1?
Ferdinand
# When ASICs generate a share, is it always at difficulty 1?

(Asked by: username_0 on 2014-12-15)

Are they preset to only return difficulty 1 shares when the find a nonce? Then mining software verifies if it meets current target difficulty? Or, if given a different target difficulty, will the ASIC only return shares that meet that difficulty setting?

If this is hardware specific, any idea which chips allow variation in the target difficulty?

The question in part stems from some misunderstandings I have seen on questions of what a share is. Whether it is always a nonce found for difficulty 1, or if it is a nonce found for the target difficulty sent to the miner. There are some confusing answers out there.

**Tags:** asic, difficulty, nonce, mining-pool-shares, miner-configuration


---

## 1 answers

### Answer by username_1 on 2015-04-06. Score: 3

It's hardware specific, and most of the information for Bitcoin mining ASIC are under an NDA so this can't be posted publicly. There's very little utility in returning difficulty one shares to the controller, for a device doing 1TH/s it would mean dealing with hundreds of results a second that the controller is just throwing away.

The difficulty of a "share" is whatever the hash target was, if we have a target of difficulty 256, then any valid block header with a difficulty more than this would make that "share" valid for the target. Shares with a vastly higher difficulty (in the billions today) might also be valid as a block for their parent pool. Shares are only used by pools to gauge how much work a client is putting into finding a block (they are simply blocks with too low of a difficulty to be valid), they're completely useless for anything else and thrown away.


---

