<p>No, it will not be possible to use Taproot on BCH after the hard fork. Taproot requires additional script constructions and interpretations of stack elements which the Schnorr signature algorithm by itself cannot provide. The BCH hard fork merely changes the signature algorithm for specific kinds of OP_CHECKSIG and OP_CHECKDATASIG outputs. No other changes related to scripts or the interpretation of stack elements is done.</p>

CC BY-SA 4.0
2019-05-07T18:44:18.640Z
To spell it out; hamfisted “first!!” implementations are a poor choice in a consensus system.
Claris
CC BY-SA 4.0
2019-05-07T14:31:37.740Z
2019-05-07T14:31:37.740Z
Ava Chow
<p>BCH is going to introduce <a href="https://github.com/bitcoincashorg/bitcoincash.org/blob/master/spec/2019-05-15-upgrade.md" rel="nofollow noreferrer">support for Schnorr signatures on May 15th</a>. One of the most anticipated features for Schnorr signatures on Bitcoin is the introduction of taproot constructions. Will it be possible to use Taproot on BCH after the upcoming fork?</p>

<bitcoin-cash><schnorr-signatures><taproot>
Is the BCH version of Schnorr signatures compatible with taproot?
Murch
# Is the BCH version of Schnorr signatures compatible with taproot?

(Asked by: username_0 on 2019-05-07)

BCH is going to introduce [support for Schnorr signatures on May 15th](https://github.com/bitcoincashorg/bitcoincash.org/blob/master/spec/2019-05-15-upgrade.md). One of the most anticipated features for Schnorr signatures on Bitcoin is the introduction of taproot constructions. Will it be possible to use Taproot on BCH after the upcoming fork?

**Tags:** bitcoin-cash, schnorr-signatures, taproot


---

## 1 answers

### Answer by username_1 on 2019-05-07. Score: 2 | Accepted answer

No, it will not be possible to use Taproot on BCH after the hard fork. Taproot requires additional script constructions and interpretations of stack elements which the Schnorr signature algorithm by itself cannot provide. The BCH hard fork merely changes the signature algorithm for specific kinds of OP\_CHECKSIG and OP\_CHECKDATASIG outputs. No other changes related to scripts or the interpretation of stack elements is done.

> **Comments:**
> **username_2**: To spell it out; hamfisted “first!!” implementations are a poor choice in a consensus system.  

---

