Analysis updated 2026-05-18
Add a standard interface like SRC-20 to a Sway smart contract for token creation.
Build a vault contract that follows the SRC-6 vault standard for holding assets.
Look up example implementations for a given standard before writing a contract.
Requires the forc toolchain (v0.70.2) and familiarity with Sway smart contract development.
This repository defines official standards for Sway, which is the smart contract programming language used on the Fuel blockchain. A smart contract is a program that runs automatically on a blockchain and controls things like digital assets or agreements. Standards like these serve a similar role to standards in any other industry: they give developers a shared set of rules so that different contracts and tools can work together predictably. The standards here cover things like how to define a digital asset (called a Native Asset on Fuel), how to handle minting and burning tokens, how to build a vault that holds assets for others, and how to attach metadata to a token. Each standard is identified by a code like SRC-20 or SRC-3, following a naming pattern similar to standards on other blockchain platforms. To use one of these standards in a Sway project, you add it as a dependency in your project's configuration file using a command-line tool called forc, then import the relevant interface into your contract code. The README includes short examples showing exactly how to do this. Some standards are still drafts, meaning they are proposed but not finalized. The project encourages developers to try drafts and give feedback. If a developer needs a standard that does not exist yet, they can open an issue to propose one. Sway itself is still being actively developed, so the standards are expected to be refined over time.
A library of official Sway language standards (like SRC-20 for tokens) that developers import to make Fuel blockchain smart contracts interoperable.
Mainly Sway. The stack also includes Sway, Fuel, forc.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.