Skip to main content

Use the Schema Tool

Creating smart contracts is simplified using the Schema Tool. This guide outlines the initial steps to set up a new smart contract from scratch.

Step 1: Establish a Central Folder

Select a central folder to house all your smart contracts. You'll create a separate subfolder for each contract within this central repository.

Next, choose a descriptive, capitalized camel case name for your contract, like MySmartContract.

Step 2: Create a Subfolder

After naming your smart contract, you should create a corresponding subfolder. Open your terminal, navigate to the central folder, and initialize your project with the Schema Tool using the following command:

schema -init MySmartContract

This command will create a subfolder named mysmartcontract and generate an initial YAML schema definition file inside this subfolder. Note that the generated subfolder name is all lower-case. This is to conform to best practices for package names in most languages. The generated schema definition file looks like this:

name: MySmartContract
description: MySmartContract description
events: {}
structs: {}
typedefs: {}
owner: AgentID // current owner of this smart contract
owner: AgentID? // optional owner of this smart contract
access: owner // current owner of this smart contract
owner: AgentID // new owner of this smart contract
owner: AgentID // current owner of this smart contract

After initializing your project with the Schema Tool, a pre-populated schema definition file will be generated in the mysmartcontract subfolder. This file contains the necessary sections and functions to manage your smart contract's ownership.

Naming Conventions

Ensure to follow the camel case naming convention in the schema definition file. Here is how to use it:

  • Function and variable names: start with a lowercase letter (e.g., myFunction)
  • Type names: start with an uppercase letter (e.g., MyType)

Customizing Fields

Begin by updating the description field with a relevant description of your smart contract. It is the perfect time to add any known definitions to the necessary sections.

Generating Initial Code

Navigate to your mysmartcontract subfolder to generate the initial code for your preferred programming language using the Schema Tool.

If you want to generate Go code, you should run the schema tool with the -go option like this:

schema -go

If you want to generate more than one language your can simply specify multiple options. For example, to generate both Rust and Go code you would specify both options like this:

schema -rs -go

The schema tool will generate a complete set of source files for the desired language(s), that will compile successfully into a Wasm code file. You compile these as follows:

tinygo build -target wasm go/main.go

This will use the Go source files in the go/mysmartcontract subfolder. The only file in this folder that you should edit manually is mysmartcontract.go. All other source files will be regenerated and overwritten whenever the schema tool is run again.

See the TinyGo documentation for more build options.

The generated code is essentially identical for each language, barring some language idiosyncrasy differences. Just view different language files with the same name next to, each other, and you will see what we mean.

Here is an example of the initially generated code, mysmartcontract.xx looks like this before you even start modifying it:

package mysmartcontract

import ""

func funcInit(ctx wasmlib.ScFuncContext, f *InitContext) {
if f.Params.Owner().Exists() {

func funcSetOwner(ctx wasmlib.ScFuncContext, f *SetOwnerContext) {

func viewGetOwner(ctx wasmlib.ScViewContext, f *GetOwnerContext) {

The schema tool automatically generates an initial working version of the functions to maintain the smart contract owner, catering to most use cases.

To streamline the building process, configure a build rule in your environment. This rule should trigger the schema tool with the necessary parameters whenever there are changes in the schema definition file. This setup ensures automatic file regeneration, eliminating the need to run the schema tool manually after each modification. The tool regenerates code only if it detects alterations since its last operation. To override this and force regeneration, include the -force flag in the command line parameter.

Video Tutorial

Creating Smart Contracts using AssemblyScript