> For the complete documentation index, see [llms.txt](https://asigna.gitbook.io/asigna/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://asigna.gitbook.io/asigna/stacks-multisig/quickstart/vault-balance/sip-10s.md).

# SIP-10s

### What Are SIP-10 Tokens?

**SIP-10** is the standard for fungible tokens on the **Stacks blockchain** — a Layer 1.5 solution bringing smart contracts and DeFi to Bitcoin. It defines how tokens behave in **Clarity smart contracts**, allowing easy integration with wallets, DAOs, and DeFi apps.\
Unlike BRC-20 or Runes, SIP-10 tokens are **fully on-chain** on Stacks and secured by **Bitcoin finality** via Proof of Transfer (PoX).

#### 🔧 How SIP-10 Works

* Tokens are managed through **Clarity smart contracts**
* Core functions include `transfer`, `get-balance`, and `get-total-supply`
* All interactions (mint, burn, send) are done via contract calls
* Supports optional metadata: name, symbol, decimals

#### 💡 Key Features

* **Smart contract-based**: Fully programmable logic
* **Bitcoin-secured**: Anchored to Bitcoin via PoX
* **DeFi-ready**: Compatible with Stacks-native dApps
* **Flexible**: Custom minting rules and access control

#### 🧱 Origin of SIP-10 Tokens

A SIP-10 token is created when a developer deploys a Clarity contract using the SIP-10 interface. The contract defines:

* Token name & symbol (e.g., `USDSTX`)
* Supply logic and minting rules
* Decimal precision (e.g., 6 or 8)
* Optional admin roles

Once deployed, the token is usable across **Stacks wallets** and dApps like **ALEX**, **Velar**, and **Arkadiko** and can be bridged to Bitcoin DeFi in wrapped formats.