<p>Very little of transaction validation logic is done in the ASIC. All that they do is take a <a href="https://en.bitcoin.it/wiki/Block_hashing_algorithm" rel="nofollow noreferrer">block header</a>, rapidly increment the nonce, and see if the hash that pops out is anywhere close to the target. So, as long as the block header doesn't change, none of the ASICs need to change.</p>
<h3>Nonce</h3>
<p>The 4-byte nonce field might need to change in the near future, because you can only have 4 billion distinct hashes every second. That might seem like a lot, but with ASICs getting 100Ghash/s, it gets a bit awkward. One way around it is to make 25 different coinbase transactions, thus getting you 25 different block headers. You then give each twenty-fifth of the ASIC a different block header. Despite all this, lengthening the nonce field is probably more trouble than it's worth, given that it would require a hard fork.</p>

CC BY-SA 3.0
2013-02-06T09:23:00.783Z
Changing the timestamp is another way.
David Schwartz
CC BY-SA 3.0
2013-02-06T16:06:24.263Z
"hashes every second" Already taken into account.
Nick ODell
CC BY-SA 3.0
2013-02-06T07:10:42.257Z
2013-02-06T07:27:33.503Z
2020-06-16T11:10:03.350Z
Nick ODell
<p>When ASIC mining devices ship, what parameters of mining become hardcoded? How would these ASIC mining devices respond to any changes to mining procedure / algorithms?</p>

<asic><mining-hardware><mining-technical-details>
What mining parameters are not modifiable with ASIC miners?
vi.su.
# What mining parameters are not modifiable with ASIC miners?

(Asked by: username_0 on 2013-02-06)

When ASIC mining devices ship, what parameters of mining become hardcoded? How would these ASIC mining devices respond to any changes to mining procedure / algorithms?

**Tags:** asic, mining-hardware, mining-technical-details


---

## 1 answers

### Answer by username_1 on 2013-02-06. Score: 3

Very little of transaction validation logic is done in the ASIC. All that they do is take a [block header](https://en.bitcoin.it/wiki/Block_hashing_algorithm), rapidly increment the nonce, and see if the hash that pops out is anywhere close to the target. So, as long as the block header doesn't change, none of the ASICs need to change.

### Nonce

The 4-byte nonce field might need to change in the near future, because you can only have 4 billion distinct hashes every second. That might seem like a lot, but with ASICs getting 100Ghash/s, it gets a bit awkward. One way around it is to make 25 different coinbase transactions, thus getting you 25 different block headers. You then give each twenty-fifth of the ASIC a different block header. Despite all this, lengthening the nonce field is probably more trouble than it's worth, given that it would require a hard fork.

> **Comments:**
> **username_2**: Changing the timestamp is another way.  
> **username_1**: "hashes every second" Already taken into account.  

---

