Follow one instrument from setup to its first transfer in the Console. You issue the asset from a template, mint tokens to a holder, and transfer part of that balance. An optional step adds your own asset class. This path covers the opening stages of the asset lifecycle, which continues through servicing and final redemption.
- Step 1 of 2: Account and organisation (done)
- Step 2 of 2: Issue your first asset
Issuing, minting and transferring each depend on the state the step before leaves.
Confirm the organisation, optionally add an asset class, issue and launch from a template, then mint to a holder and transfer part of the balance.
Roles. To issue an asset, your wallet needs the Asset manager role. Your wallet is the account that signs for you on the network and holds your roles and balances. If you created the organisation, your wallet already holds Permission manager, System manager, Asset manager, Compliance manager, Verification policy manager, Identity manager and Verification issuer, so you can issue at once. If you joined by invitation, you hold the roles the invitation carried, and a Permission manager grants any that are missing on Roles and permissions. The optional asset class step needs the Permission manager, System manager or Asset designer role. The wallet that issues the asset receives Permission manager, Governance, Supply management and Emergency on it, so the same wallet can mint and launch it. The Console checks these roles for the signed-in account, and the forms have no role selector.
PIN. The Console asks you to confirm every action your wallet signs with your transaction PIN or transaction code. If you skipped that setup after onboarding, the Console opens it before your first signing action, or you can set it now on Security.
Template. An instrument template defines the facts, on-chain behaviour and compliance rules for one product shape. Only a Permission manager, System manager or Asset designer can create or publish one, so this tutorial uses the templates already published in your organisation. The person who owns the product at your institution decides which template and which configuration to select. That decision is separate from the Console role that lets you act on it. Read Instrument templates and Compliance policy to understand the template and compliance choices this tutorial takes as given.
Recipients. The first holder you mint to and the recipient of the transfer each need a verified identity that meets the asset's rules, because the token checks both a mint and a transfer. Use Verify a participant to review a participant's status before you mint. Mint to your own signed-in wallet, so the transfer step has a balance to send from. Get the transfer recipient's wallet address before the transfer step.
Steps
Confirm the organisation
Open the account menu at the top right and confirm that it names the organisation you created. The asset classes, issued assets and roles you work with belong to the active organisation.
Optional: add an asset class
Skip this step to issue from a published template, because the Console sets the asset class from the template you choose. An asset class is the economic category an instrument belongs to, such as Equity, Fixed income or Funds. Adding one needs the Permission manager, System manager or Asset designer role. The instrument template you choose in a later step decides the token's facts, behaviour and compliance rules. Open “Asset design”, then “Asset classes”. Select “Add asset class”, enter a name and description, and select “Create”. The Console generates the URL-safe slug from the name.
The “Asset classes” table lists each class with its slug and a “System” or “Custom” badge, with “Add asset class” above it.
Start a new issue
Open “All assets” and select “Issue asset”. Choose a published instrument template. The list shows the templates your organisation has published. Common Equity, Corporate Bond and Fiat-Backed Stablecoin start published. When the template you need is missing, a Permission manager, System manager or Asset designer publishes it on Instrument templates. The choice determines which details and features Issue asset asks you to configure.
“Issue asset” opens on the “Instrument” step, where “Choose an instrument” lists the published templates in one table.
Before you pick a template, the step list shows “General info”, “Holder rule”, “Asset permissions”, “Token logo” and “Review” after it. The table has a search field and the “Class” and “Features” filters. Common Equity, Corporate Bond and Fiat-Backed Stablecoin start published, and the demo organisation in this capture has published more.
Configure and issue the asset
Complete each step shown for the selected instrument. Enter the asset basics. The Console sets the asset class from the template you chose. Fill in the instrument details the template leaves open, then the compliance values your product owner approved, the initial permissions and an optional logo. Check the template and the decimals on the review before you issue, because neither can change on a live instrument. On “Review”, select “Open for transfers once issued” so the asset can accept mint and transfer operations immediately. Enter your PIN when the Console asks you to confirm your identity, then submit the issue. The Console shows the asset name followed by “is issued” and opens the new asset.
A successful issue deploys a composable token: one regulated token contract, configured at creation with the features and compliance rules your template and settings specify. Every product shape uses the same contract. The instrument starts with no minted supply. “Open for transfers once issued” makes it ready for the next step. If you did not select “Open for transfers once issued”, the asset is halted. Open “Actions” on the asset's page and select “Resume token operations”. The first resume launches the token. Confirm that transaction before minting.
Mint tokens
Open “All assets”, select the asset, open “Actions” and select “Mint tokens”. Enter the first holder's wallet address and the amount, using your own signed-in wallet so you can transfer from it next. The form checks that wallet's eligibility against the asset's rules as you enter it, before you can submit. Review the mint, then select “Confirm mint”. The Console reports “Tokens minted successfully” when the transaction completes. To undo a mint on a token that supports burning, use “Burn tokens” in the same “Actions” menu. The burn is a separate transaction.
“All assets” lists issued assets.
Open one row to reach its supply and transfer tools.
Transfer tokens
On the asset's page, open “Actions” and select “Transfer tokens”. The signed-in wallet must hold a balance of the asset, which it does when you minted to it. Enter the recipient and amount, then submit the transfer. Transfer-path compliance enforces the configured rules inside the token's own on-chain transfer, so every ordinary transfer runs the same check, whichever surface submits it. If any rule fails, the transfer reverts on chain before any balance changes, and the Console reports the failure. A successful transfer shows “Tokens transferred successfully”. To undo a completed transfer, the recipient sends a new transfer back.
Continue with Where to go next.