Define the class
Create a token with its own identity and policy. Applications can distinguish custom assets from the network’s native currency.
Assets with an explicit policy
Create a token for what your application values.
Define a custom token class and manage minting, burning, transfers, and policy through Sigil’s native token surface.
Custom TokensIllustrated study
Agreement / evidence / terms
Settlement remains subject to terms and verification.
01 / Built for a purpose
Start with the asset’s rules.
An application may need its own unit of access, participation, or value. Sigil’s custom token surface separates the token class and its policy from the individual operations that change balances and supply.
Control issuance
Minting follows the class’s authorization rules. The operation records an increase in supply and the balance receiving it.
Move and retire balances
Native transfer and burn operations cover ordinary ownership changes and supply reduction without requiring a custom contract for each action.
Make policy visible
The token’s policy is part of its state. Interfaces can explain who controls the class rather than treating every asset as if it had identical permissions.
02 / From intent to outcomeA clear path through
A clear path through
custom tokens.
- 01
Define
Specify the token class and its controlling policy.
- 02
Issue
Mint balances through an authorized transaction.
- 03
Use
Transfer, burn, and query balances as the application’s workflow requires.
The details matterGood questions.
Good questions.
Clear answers.
Is a custom token the native MINT currency?
No. MINT pays for mainnet activity. A custom token is a separate asset with its own class and policy.
Does creating a token create a market for it?
No. Token creation establishes the asset. Distribution, liquidity, pricing, and application utility are separate decisions.
Keep exploringOne capability.