cashscript VS libauth

https://cashscript.org/ (check out the guides!)

CashScript is similar to solidity, but writing contracts for UTXO chains is slightly different than for EVM chains since you don't have global state, just utxos.

This is a stripped down example from p2pkh.cash showing a simple authorized address example:

Closest is probably cashscript. I believe they are currently working on these for the May upgrade this year

This app was built using the Cashscript route. So the contracts are written in a solidity style language and then transpiled to BitcoinScript. They're fast to write and easy to read, HOWEVER, if you step through the actual bitcoin script, you'll often see a number of things that are not optimal. There is a playground for CashScript: https://playground.cashscript.org/

I should clarify that by examples I mean working code that can be run by itself as a demo. For example, the next.js repository has a very large collection of examples for integrating next.js with various tools and frameworks. You can also see these type of examples in the cashscript repository as well as in the bch-js repos

You can also use https://cashscript.org/

Related GH Issue: https://github.com/rkalis/cashscript/issues/131

Note that a smart wallet for Bitcoin-tech doesn't exist, so if you implement a contract, you need to "teach" some wallet how to spend from the template. Dream is to have an universal wallet that can easily import contract templates, things like LibAuth and BitauthIDE were built with that goal, we're getting there!

To craft the transactions you'd also need a library, maybe something like https://libauth.org/ or you could craft the transactions by hand by reading on https://documentation.cash/

I've also written descriptions of all VM operations for Libauth: https://libauth.org/enums/opcodedescriptionscommon.html and https://libauth.org/enums/opcodedescriptionsuniquebch.html

I've been building this "user space" tooling in Libauth (a lightweight, zero-dependency JS/TS library), and I would love to work with anyone interested on building that tooling in other languages/libraries too!