• English
  • Русский

# Asset Script

Asset script verifies transactions within the asset (token), that is, allows or denies the transaction depending on the specified conditions.

Asset with a script assigned to it is called a smart asset.

⚠️ Please note:

  • The asset script can only verify transactions, but not orders.
  • If a token is issued without a script, then the script cannot be added later.
  • The script cannot be removed, so it is impossible to turn a smart asset into a regular one.
  • Smart asset cannot be a sponsored asset.

# Asset Script Format

The script code is composed of the following parts:

# Directives

The asset script should start with directives:

{-# STDLIB_VERSION 8 #-}
{-# CONTENT_TYPE EXPRESSION #-}
{-# SCRIPT_TYPE ASSET #-}

The above directives tell the compiler that:

  • the script uses the Standard library version 8,
  • the script contains a boolean expression,
  • the script will be assigned to an asset.

# Auxiliary Definitions

After the directives, you can define auxiliary variables and functions.

Example:

let someConstant = 42
func doSomething () = {
    height + someConstant
}

# Boolean Expression

The expression checks transactions involving the asset for compliance with the specified conditions. If the conditions are not met, the transaction is denied. Possible results of evaluating the expression are:

  • true: the transaction is allowed,
  • false: the transaction is denied,
  • an error: the transaction is denied.

Using the match ... case operator, you can set up different conditions depending on the type of the transaction. For example, the following expression prohibits changing the asset script and allows other transactions:

match tx {
  case t : SetAssetScriptTransaction => false
  case _ => true
}

# Failed Transactions

If the asset script denies the Exchange transaction when a block generator adds the transaction to a block (provided that the sender signature verification or the account script verification passed), the transaction is saved on the blockchain but marked as failed ("applicationStatus": "script_execution_failed"). The sender of the transaction (matcher) is charged a fee. The transaction doesn't entail any other changes in balances, in particular, the order senders don't pay the matcher fee.

If the asset script denies the Invoke Script transaction when a block generator adds the transaction to a block (provided that the sender signature verification or the account script verification passed and the complexity of calculations performed by dApp script exceeded the threshold for saving failed transactions), the transaction is saved on the blockchain but marked as failed ("applicationStatus": "script_execution_failed"). The transaction sender is charged a fee. The transaction doesn't entail any other changes on the blockchain.

More about transaction validation

More about handling failed transactions

# Data Accessible to Asset Script

The following data can be used for checks:

  • Blockchain data: current height, account balances, entries in account data storages, parameters of tokens, etc.
  • Fields of the current verified transaction, excluding proofs. The built-in variable tx contains this transaction. The set of fields depends on the type of transaction, see the Transaction Structures chapter.

# Examples

Find the asset scripts examples:

Account Script
Standard Library