<p>For now (or even post Taproot activation in November) they have no use and shouldn't be used in any scripts. However as the excerpt above says, making multiple previously disabled opcodes OP_SUCCESS in the Taproot soft fork means new opcode functionality can be easily added in future soft forks post Taproot. Old clients that don't update for future soft forks will automatically treat scripts with these new opcodes as valid and hence they won't be forked off the network by new clients validating the use of these new opcodes.</p>
<p>Some new opcodes that are being considered for future soft forks are <a href="https://github.com/bitcoin/bips/blob/master/bip-0119.mediawiki" rel="nofollow noreferrer">OP_CHECKTEMPLATEVERIFY</a>, <a href="https://medium.com/blockstream/cat-and-schnorr-tricks-i-faf1b59bd298" rel="nofollow noreferrer">OP_CAT</a>, OP_CHECKSIGFROMSTACK etc.</p>
<p>Other upgradeability features in Taproot (BIP 341) are discussed <a href="https://bitcoin.stackexchange.com/questions/96951/what-are-the-different-upgradeability-features-in-the-bip-taproot-bip-341-prop">here</a>.</p>

CC BY-SA 4.0
2021-08-31T12:06:20.193Z
Thanks @user253751. Updated.
Michael Folkson
CC BY-SA 4.0
2021-08-31T09:39:05.367Z
2021-08-31T12:06:05.500Z
2021-08-31T12:06:05.500Z
Michael Folkson
<p><a href="https://i.sstatic.net/QjEdu.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/QjEdu.png" alt="enter image description here" /></a></p>
<p>What is the use of the updated op_success operation code?</p>

<bitcoin-core><taproot>
What is the latest bitcoin script connection string operation code?
M Yang
# What is the latest bitcoin script connection string operation code?

(Asked by: username_0 on 2021-08-31)

[![enter image description here](https://i.sstatic.net/QjEdu.png)](https://i.sstatic.net/QjEdu.png)

What is the use of the updated op\_success operation code?

**Tags:** bitcoin-core, taproot


---

## 1 answers

### Answer by username_1 on 2021-08-31. Score: 2

For now (or even post Taproot activation in November) they have no use and shouldn't be used in any scripts. However as the excerpt above says, making multiple previously disabled opcodes OP\_SUCCESS in the Taproot soft fork means new opcode functionality can be easily added in future soft forks post Taproot. Old clients that don't update for future soft forks will automatically treat scripts with these new opcodes as valid and hence they won't be forked off the network by new clients validating the use of these new opcodes.

Some new opcodes that are being considered for future soft forks are [OP\_CHECKTEMPLATEVERIFY](https://github.com/bitcoin/bips/blob/master/bip-0119.mediawiki), [OP\_CAT](https://medium.com/blockstream/cat-and-schnorr-tricks-i-faf1b59bd298), OP\_CHECKSIGFROMSTACK etc.

Other upgradeability features in Taproot (BIP 341) are discussed [here](https://bitcoin.stackexchange.com/questions/96951/what-are-the-different-upgradeability-features-in-the-bip-taproot-bip-341-prop).

> **Comments:**
> **username_1**: Thanks @user253751. Updated.  

---

