Contracts that
cannot surprise you

An expression language for deciding whether a transaction is allowed and, in a dApp, for changing account state. Every script has a complexity cost the node computes at deployment, and scripts over the budget are rejected outright rather than at run time.

What that buys you is the absence of a whole class of failure. There is no gas to estimate and no out-of-gas halfway through a state change, because the cost of a script is a property known before it ever runs.

You can confirm this yourself rather than taking it from a page: features 15 and 16 read ACTIVATED on the features table, and 17 is not in it.

• An account. Feature 4, Smart Accounts. The script vets every transaction the account signs: multisig, time locks, spending rules.
• An asset. Feature 9, Smart Assets. The script vets every transfer of that asset: whitelists, freezes, transfer restrictions.
• A dApp. Feature 11. Callable functions that hold their own state and accept payments, invoked by an InvokeScript transaction.

The compiler is published to npm and compiled from Scala through Scala.js, so it runs in a browser with no server involved. That is unusual and worth using: you can compile and check a contract client-side without sending source anywhere.

npm i @decentralchain/ride-lang @decentralchain/ride-repl

On the JVM the same language is io.decentralchain:lang_3 on Maven Central, with lang-testkit_3 beside it for tests.

DecentralSwap is a constant-product AMM built from two RIDE contracts, both deployed on mainnet. If you want to see what a non-trivial RIDE system looks like in production rather than in an example, that is the one to read.