Issue, mint, and transfer your first asset in DALP

Follow one instrument from setup to its first transfer in the Console. You create its classification, issue the asset from a template, mint tokens to a holder, and transfer part of that balance. This path covers the opening stages of the asset lifecycle, which continues through servicing and final redemption.

Five steps build on each other: confirm the organisation, add an asset class, issue an instrument from a template, mint its tokens, then transfer part of the balance. The figure below shows the state each step leaves behind, since later steps depend on what the step before it produced.

Confirming the organisation gives you a scope for everything that follows. Adding an asset class gives you a category to issue into. Issuing an instrument deploys one configured token contract, with no supply yet. Minting puts a token balance in a holder's wallet. Transferring moves part of that balance to a second holder, and the platform's transfer rules check the recipient automatically before the balance moves.

Before you start

Complete Create your account and organisation. You need administrator access to issue an asset. An administrator, system manager, or asset designer can configure asset classes and templates before issuance. You also need the supply-management role to mint and the emergency role to unpause the asset. A transfer needs a wallet with a token balance. The Console checks these roles for the signed-in account; the forms have no role selector. An instrument template defines the facts, on-chain behavior, and compliance rules for one product shape. Only an administrator, system manager, or asset designer can create or publish one, so treat the templates already in your catalog as approved starting points rather than something this tutorial asks you to build. Someone at your institution who owns that product, its business terms and its compliance configuration, decides which template and which configuration to select; that decision is separate from the Console access role that lets you act on it. Obtain the recipient's wallet address before the transfer step; the Console checks the configured rules against it automatically when you submit.

Use Admins and roles to see who holds administrator and supply-management access. Read Instrument Templates and Compliance Policy for the choices that this tutorial treats as approved inputs. Use Verify a participant before the transfer when the recipient's status needs review.

Steps

Confirm the organisation

Open the organisation switcher and confirm that the organisation you created is active. Its asset classes and issued assets stay in this scope. The same is true for roles and balances.

Add an asset class

An asset class is the economic category an instrument belongs to, such as Equity, Fixed income, or Funds; it is what you browse to find a template, not the template itself. The instrument template you choose in a later step decides the token's actual facts, behavior, 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.

Asset classes page with the Add asset class action — Screen equivalent: asset classes group instruments and templates. System classes and organisation-created classes carry distinct labels.

Start a new issue

Select "Issue new asset" in the Console navigation. Choose the approved instrument template. The list shows the templates your organisation has published; Equity, Bond, and Stablecoin start published. When the template you need is missing, an administrator, system manager, or asset designer publishes it on Instrument templates. The choice determines which details and features the designer asks you to configure.

Issue new asset screen with instrument choices — Screen equivalent: the asset designer starts with the instrument choice. Only instruments whose factories are available can be selected.

Configure and issue the asset

Complete each designer step shown for the selected instrument. Enter the asset basics and classification, using the asset class you just created. Set its permissions and features, then apply the compliance configuration your product owner approved. Check the locked facts and instrument type before issuing; these choices cannot change on a live instrument. In the summary, select "Unpause after creation" so the asset can accept mint and transfer operations. Enter your PIN when the Console asks you to confirm your identity, then submit the issue.

A successful issue deploys a composable token: one regulated token contract, configured at creation with the features and compliance rules your template and settings specified, instead of a separate contract built and audited for each product shape. The instrument starts with no minted supply. "Unpause after creation" makes it ready for the next step. If you leave it paused, select "Unpause token" from the asset's management menu and confirm that transaction before minting. The Console shows "Token Created Successfully".

Mint tokens

Open "All assets", select the asset, and choose "Mint tokens" from its manage menu. Add the recipient's wallet address and amount. 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. Minting is not reversible from this screen: undoing it means transferring the tokens back or burning them, each a separate step you take deliberately.

All assets table with issued assets available for management — Screen equivalent: "All assets" lists issued assets. Open one row to reach its supply and transfer tools.

Transfer tokens

Open "Transfer tokens" for a wallet that holds the asset. Enter the recipient and amount, then submit the transfer. Transfer-path compliance enforces the configured rules inside the token's own on-chain transfer, not as a separate check the Console or the API performs beside it; every 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 transaction shows "Tokens transferred successfully", and like the mint before it, a completed transfer is undone only by submitting a new transfer back, never by canceling this one.

Issue your first asset