<blockquote>
  <p>Once segwit shall be activated, does it mean that ASIC miners using ASICBoost miners won't be able to mine on that chain at all anymore?</p>
</blockquote>

<p>No. Nothing about segwit prevents miners from mining non-segwit blocks using ASICBOOST. Mining segwit blocks will slow down (and likely prevent) covert ASICBOOST from working, but miners can still use it and also use overt ASICBOOST if they want to.</p>

<blockquote>
  <p>What about when UASF activates on august 1st 2017 (if it activates)? Does it mean that UASF nodes won't accept block found by ASIC miners using ASICBoost?</p>
</blockquote>

<p>No. It means that all blocks must signal for segwit so that segwit activates under the BIP 141 activation rules. This has nothing to do with ASICBOOST and does not require segwit commitments in blocks until after activation. After activation, segwit commitments are only required in blocks containing segwit transactions which not all miners must have in their blocks.</p>

<blockquote>
  <p>Are all the current ASICs using ASICBoost good for the trash should the UASF chain win?</p>
</blockquote>

<p>No. Segwit itself does not prevent ASICBOOST. It only partially prevents covert ASICBOOST, and only for blocks that include the segwit commitment (i.e. blocks containing segwit transactions). In order for covert ASICBOOST to be blocked, all blocks would need to have a segwit commitment in them regardless of including segwit transactions, but that is not something that segwit specifies.</p>

CC BY-SA 3.0
2017-06-19T20:09:29.027Z
Furthermore, covert ASICBoost is not observable, so by definition the resulting blocks can't be made invalid as the blocks aren't distinguishable from others. At best, some changes may make the optimization useless (so using it just doesn't benefit the miner anymore), but as explained, BIP148 does not even do that.
Pieter Wuille
CC BY-SA 3.0
2017-06-19T22:43:10.420Z
"It means that all blocks must signal for segwit so that segwit activates under the BIP 141 activation rules." Should that actually be **BIP-148** instead of BIP-141? I thought BIP-141 only defined what SegWit, BIP-148, BIP-149, etc. deal with how it should be activated, right?
MrJLP
CC BY-SA 3.0
2017-06-19T22:45:54.377Z
No. BIP 141 contains the actual original segwit deployment parameters. BIP 148 is an extension on the BIP 141 deployment parameters. BIP 149 is an entirely different deployment that does not use BIP 9 deployment specifications.
Ava Chow
CC BY-SA 3.0
2017-06-19T04:31:38.310Z
2017-06-19T04:31:38.310Z
Ava Chow
<p>If UASF activates, are blocks found by ASICBoost still valid on UASF nodes?</p>

<p>I understand that segwit is a softfork and that hence the segwit changes makes some blocks that were previously valid now invalid (including those using tx malleability).</p>

<p>I've got basically one question but I cannot formulate it well enough, so I'm breaking it into several questions.</p>

<p>Once segwit shall be activated, does it mean that ASIC miners using ASICBoost miners won't be able to mine on that chain at all anymore?</p>

<p>What about when UASF activates on august 1st 2017 (if it activates)? Does it mean that UASF nodes won't accept block found by ASIC miners using ASICBoost?</p>

<p>Are all the current ASICs using ASICBoost good for the trash should the UASF chain win? </p>

<bip148-uasf><asicboost>
If UASF activates, are blocks found by ASICBoost still valid on UASF nodes?
Cedric Martin
# If UASF activates, are blocks found by ASICBoost still valid on UASF nodes?

(Asked by: username_0 on 2017-06-19)

If UASF activates, are blocks found by ASICBoost still valid on UASF nodes?

I understand that segwit is a softfork and that hence the segwit changes makes some blocks that were previously valid now invalid (including those using tx malleability).

I've got basically one question but I cannot formulate it well enough, so I'm breaking it into several questions.

Once segwit shall be activated, does it mean that ASIC miners using ASICBoost miners won't be able to mine on that chain at all anymore?

What about when UASF activates on august 1st 2017 (if it activates)? Does it mean that UASF nodes won't accept block found by ASIC miners using ASICBoost?

Are all the current ASICs using ASICBoost good for the trash should the UASF chain win?

**Tags:** bip148-uasf, asicboost


---

## 1 answers

### Answer by username_1 on 2017-06-19. Score: 1

> Once segwit shall be activated, does it mean that ASIC miners using ASICBoost miners won't be able to mine on that chain at all anymore?

No. Nothing about segwit prevents miners from mining non-segwit blocks using ASICBOOST. Mining segwit blocks will slow down (and likely prevent) covert ASICBOOST from working, but miners can still use it and also use overt ASICBOOST if they want to.

> What about when UASF activates on august 1st 2017 (if it activates)? Does it mean that UASF nodes won't accept block found by ASIC miners using ASICBoost?

No. It means that all blocks must signal for segwit so that segwit activates under the BIP 141 activation rules. This has nothing to do with ASICBOOST and does not require segwit commitments in blocks until after activation. After activation, segwit commitments are only required in blocks containing segwit transactions which not all miners must have in their blocks.

> Are all the current ASICs using ASICBoost good for the trash should the UASF chain win?

No. Segwit itself does not prevent ASICBOOST. It only partially prevents covert ASICBOOST, and only for blocks that include the segwit commitment (i.e. blocks containing segwit transactions). In order for covert ASICBOOST to be blocked, all blocks would need to have a segwit commitment in them regardless of including segwit transactions, but that is not something that segwit specifies.

> **Comments:**
> **username_2**: Furthermore, covert ASICBoost is not observable, so by definition the resulting blocks can't be made invalid as the blocks aren't distinguishable from others. At best, some changes may make the optimization useless (so using it just doesn't benefit the miner anymore), but as explained, BIP148 does not even do that.  
> **username_3**: "It means that all blocks must signal for segwit so that segwit activates under the BIP 141 activation rules." Should that actually be **BIP-148** instead of BIP-141? I thought BIP-141 only defined what SegWit, BIP-148, BIP-149, etc. deal with how it should be activated, right?  
> **username_1**: No. BIP 141 contains the actual original segwit deployment parameters. BIP 148 is an extension on the BIP 141 deployment parameters. BIP 149 is an entirely different deployment that does not use BIP 9 deployment specifications.  

---

