The development of Bitcoin Cash, BCH, is in full gear as over the last six months, the cryptocurrency has seen several additions to its technology. The addition of technologies such as the simple Ledger protocol, Schnorr signatures, opcodes, cashshuffle, the programming language spedn, and token dividend payments have worked towards improving on the network’s resourcefulness.

However, in the bitcoin cash platform, a component that has been witnessing steady development is Cashscript, which is a complex language, applied for bitcoin cash and that was created by the software developer, Rosco Kalis. Many cryptocurrency websites and enthusiasts have made reports on Cashscript. Kalis talked about the number of innovative concepts that cashscript can facilitate. He says that the motivation for Cashscript developers is to increase the ease with which other engineers can plug a Cashscript contract into any other web application.

He is quoted as to say “For this workflow, as well as the syntax of the language, we took a lot of inspiration from Ethereum’s solidity language and web3.js/ Truffle libraries.”

Ever since, Kalis and fellow developers such as Gabriel Cardona the creator of bitbox have been making strategies and moves all the while showing the BCH community what exactly Cashscript is capable of.

Cardona earlier this week explained “Cashscript is a paradigm shift in expressiveness for BCH contracts.”

He then went a long way into shedding the spotlight on a bunch of experiments that bitbox was conducting. Cardona also tweeted a number of times on Twitter to show just what the potential of cashscript was. While showing reported Cashscript examples on Twitter, Cardona was quick to tip his hat to some of the developers who helped build on those ideas. The developers include Rosco Kalis, Emil Oldenburg, Chris Pacia, and Tobias Ruck.

On August 25, Cardona also showed the public a wager contract from Emile Oldenburg’s onchain bet example from taking OP_checkdatasig out for a test drive.” The most exciting thing about the contract was that it was written in Cashscript and executed an onchain bet between two parties. The catch being that it would only be settled by block height and price signed by an Oracle.

Developers have already shown the world that such types of transactions and contracts can work without having to change the current BCH set of code. A number of onchain wagers, oracles, and digital currency inheritance games have been built using the BCH rule set that was initially applied, but as of current, it is safe to say that Cashscript is budding fast and is enabling developers to employ the language to execute these aforementioned decision-based transactions into their workflow.

What's your reaction?
Leave a Comment