user31277: Bitcoin’s Script is the forth-like, non-Turing complete language used for transactions. However, in practice, a very limited number of kinds of scripts are allowed, a number of opcodes have been disabled, and even a number of bugs in script have to be replicated to maintain consensus.
Have there been any innovations by the altcoin community, in their forks of Bitcoin’s Script? Any with non-secp256k1 crypto? Any with more functional bignum / arbitrary integer functionality that can do cryptographic primitives? Any that add Turing complete functionality?

user137501: Bitcoin Cash is a code and blockhain fork (blocks 0 to 478558 are the same on both blockchains) which did the following upgrades to Bitcoin Script VM:

2017 Malleability fixes

Mandatory use of SCRIPT_VERIFY_STRICTENC
Enforcement of LOW_S signatures and NULLFAIL (BIP-0146)


2018

OP_CAT, OP_SPLIT, OP_AND, OP_OR, OP_XOR, OP_DIV, OP_MOD, OP_BIN2NUM, OP_NUM2BIN
OP_CHECKDATASIG, OP_CHECKDATASIGVERIFY, and more malleabiliy fixes ("push only" and "clean stack" rules). This made the precedent of allowing Script to "look" at other inputs & outputs in the same transaction, which enabled first covenants.


2019

Schnorr signatures
Schnorr multisig, and more malleability fixes (minimal push and minimal number encoding)


2020

OP_REVERSEBYTES


2021

Allow multiple OP_RETURNs


2022

SriptVM 64-byte integer support, enabled OP_MUL
Native introspection opcodes: OP_INPUTINDEX, OP_ACTIVEBYTECODE, OP_TXVERSION, OP_TXINPUTCOUNT, OP_TXOUTPUTCOUNT, OP_TXLOCKTIME, OP_UTXOVALUE, OP_UTXOBYTECODE, OP_OUTPOINTTXHASH, OP_OUTPOINTINDEX, OP_INPUTBYTECODE, OP_INPUTSEQUENCENUMBER, OP_OUTPUTVALUE, OP_OUTPUTBYTECODE


2023 P

CashTokens - native consensus-enforced UTXO token primitives and ScriptVM opcodes (OP_UTXOTOKENCATEGORY, OP_UTXOTOKENCOMMITMENT, OP_UTXOTOKENAMOUNT, OP_OUTPUTTOKENCATEGORY, OP_OUTPUTTOKENCOMMITMENT, OP_OUTPUTTOKENAMOUNT) to integrate them with contracts
Address the hash collision problem by enabling a 32-byte BIP-0016 output pattern - P2SH32




31277: <p>Bitcoin’s Script is the forth-like, non-Turing complete language used for transactions. However, in practice, a very limited number of kinds of scripts are allowed, a number of opcodes have been disabled, and even a number of bugs in script have to be replicated to maintain consensus.</p>

<p>Have there been any innovations by the altcoin community, in their forks of Bitcoin’s Script? Any with non-secp256k1 crypto? Any with more functional bignum / arbitrary integer functionality that can do cryptographic primitives? Any that add Turing complete functionality?</p>
 137501: <p>Bitcoin Cash is a code and blockhain fork (blocks 0 to 478558 are the same on both blockchains) which did the following upgrades to Bitcoin Script VM:</p>
<ul>
<li><strong>2017</strong> Malleability fixes
<ul>
<li><a href="https://documentation.cash/protocol/forks/bch-uahf#req-6-4-mandatory-use-of-script_verify_strictenc" rel="nofollow noreferrer">Mandatory use of SCRIPT_VERIFY_STRICTENC</a></li>
<li><a href="https://documentation.cash/protocol/forks/hf-20171113#summary" rel="nofollow noreferrer">Enforcement of LOW_S signatures and NULLFAIL (BIP-0146)</a></li>
</ul>
</li>
<li><strong>2018</strong>
<ul>
<li><a href="https://documentation.cash/protocol/forks/may-2018-reenabled-opcodes" rel="nofollow noreferrer">OP_CAT, OP_SPLIT, OP_AND, OP_OR, OP_XOR, OP_DIV, OP_MOD, OP_BIN2NUM, OP_NUM2BIN</a></li>
<li><a href="https://documentation.cash/protocol/forks/hf-20181115#summary" rel="nofollow noreferrer">OP_CHECKDATASIG, OP_CHECKDATASIGVERIFY, and more malleabiliy fixes (&quot;push only&quot; and &quot;clean stack&quot; rules)</a>. This made the precedent of allowing Script to &quot;look&quot; at other inputs &amp; outputs in the same transaction, which enabled first covenants.</li>
</ul>
</li>
<li><strong>2019</strong>
<ul>
<li><a href="https://documentation.cash/protocol/forks/hf-20190515#summary" rel="nofollow noreferrer">Schnorr signatures</a></li>
<li><a href="https://documentation.cash/protocol/forks/hf-20191115#summary" rel="nofollow noreferrer">Schnorr multisig, and more malleability fixes (minimal push and minimal number encoding)</a></li>
</ul>
</li>
<li><strong>2020</strong>
<ul>
<li><a href="https://documentation.cash/protocol/forks/hf-20200515#op_reversebytes" rel="nofollow noreferrer">OP_REVERSEBYTES</a></li>
</ul>
</li>
<li><strong>2021</strong>
<ul>
<li><a href="https://documentation.cash/protocol/forks/chips/2021-05-multiple-op-returns-for-bitcoin-cash" rel="nofollow noreferrer">Allow multiple OP_RETURNs</a></li>
</ul>
</li>
<li><strong>2022</strong>
<ul>
<li><a href="https://documentation.cash/protocol/forks/chips/2022-05-bigger-script-integers#summary" rel="nofollow noreferrer">SriptVM 64-byte integer support, enabled OP_MUL</a></li>
<li><a href="https://documentation.cash/protocol/forks/chips/2022-05-native-introspection-opcodes" rel="nofollow noreferrer">Native introspection opcodes</a>: OP_INPUTINDEX, OP_ACTIVEBYTECODE, OP_TXVERSION, OP_TXINPUTCOUNT, OP_TXOUTPUTCOUNT, OP_TXLOCKTIME, OP_UTXOVALUE, OP_UTXOBYTECODE, OP_OUTPOINTTXHASH, OP_OUTPOINTINDEX, OP_INPUTBYTECODE, OP_INPUTSEQUENCENUMBER, OP_OUTPUTVALUE, OP_OUTPUTBYTECODE</li>
</ul>
</li>
<li><strong>2023 P</strong>
<ul>
<li><a href="https://github.com/bitjson/cashtokens" rel="nofollow noreferrer">CashTokens</a> - native consensus-enforced UTXO token primitives and ScriptVM opcodes (OP_UTXOTOKENCATEGORY, OP_UTXOTOKENCOMMITMENT, OP_UTXOTOKENAMOUNT, OP_OUTPUTTOKENCATEGORY, OP_OUTPUTTOKENCOMMITMENT, OP_OUTPUTTOKENAMOUNT) to integrate them with contracts</li>
<li><a href="https://gitlab.com/0353F40E/p2sh32/-/blob/main/CHIP-2022-05_Pay-to-Script-Hash-32_(P2SH32)_for_Bitcoin_Cash.md" rel="nofollow noreferrer">Address the hash collision problem by enabling a 32-byte BIP-0016 output pattern - P2SH32</a></li>
</ul>
</li>
</ul>
