Issue new asset
Configure and deploy a new asset from an approved instrument template in the Console.
Issue new asset deploys a new, live token contract on chain from an approved instrument templateAn Instrument Template lets an issuer configure a new instrument from an approved shape, instead of re-deciding what it records, does, and permits each time.Read the concept. Once deployment completes, the token exists as a real contract that holders can hold and the platform tracks like any other asset. The template you pick on the first step decides the rest of the wizard. Switch to a different one later, and every entry you made so far clears. Two different templates rarely ask the same questions.
Use this page once the asset class, the instrument template, its permission assignments, and its compliance configuration have already been approved elsewhere in your institution's process. The wizard is the deployment step, not the approval step: it turns those approved choices into transactions and a deployed composable tokenA Composable Token lets an issuer bring a new regulated instrument to market by configuring facts, features, and rules, not new contract code.Read the concept. Turn to "All assets" instead when you want to browse or manage a token that already exists; this page never lists existing tokens and offers no way to edit one. The Console hides "Issue new asset" entirely from an account that lacks token-create permission, so if you cannot find the entry point at all, that permission is the first thing to check.
The wizard runs five step groups in a fixed order: "Choose instrument", "Configure details", "Compliance details", "Permissions", and "Summary". Compliance is not a placeholder that renders empty when a template needs no configuration; it drops out of the sequence entirely, so a template with a fixed compliance preset jumps straight from configuration to permissions. Selecting the instrument template also selects its asset class.
Two protections sit before the point of no return. The Console blocks a duplicate name/symbol/decimals combination before you can submit. When a template will deploy with no compliance controls, the summary states this in its own words: "Asset will deploy without compliance controls. This cannot be undone after deployment." Past that point, submitting starts a real deployment. A failed attempt leaves your entered values intact for a retry, but a successful one cannot be reversed from the Console. You cannot delete or undo a deployed asset.
Steps
Start the asset designer
Open "Asset management", then "Issue new asset". The first step, "Choose your instrument", lists the templates your organisation has published and not hidden, and sets your asset class the moment you pick one; there is no separate asset-class step to complete afterward.
The list is short at first. Three DALP Library templates start published in every organisation: Equity, Bond, and Stablecoin. Every other template appears after someone with the Admin, System manager, or Asset designer role publishes it on Instrument templates. A structure, such as a dual-class share or a convertible note, can be chosen only when your organisation has published the structure and every template in it, and none of them is hidden. Both DALP Library structures start unpublished, so the list leaves them out until someone publishes them on the "Structures" tab of Instrument templates.
When you hold one of those roles, a line under the list says you can publish more templates and links to the instrument templates overview. Other accounts do not see that line.
When your organisation offers no template at all, the step shows "No instrument templates are published" instead of a list. With a managing role you get an "Open instrument templates" link to publish one. Without it, the step tells you to ask an asset designer or administrator. This is different from a search that matches nothing, which keeps the list's search box and reads "No templates match your search or filter."
Picking a template fixes more than your asset class. The figure below shows everything it decides at once, and what changing your mind afterward costs you.
Screen equivalent: the first step lists the instrument templates your organisation has published, each showing the features and requirements it carries. An account that can manage templates sees a link to publish more under the list.
Picking a template on the first step fixes four things at once: the asset class, whether a denomination asset must already exist, which compliance step appears if any, and which fields the later steps ask for. Reselecting the same template keeps whatever you already entered; switching to a different template clears those entries.
Configure the instrument
Complete "Configure details" for the asset's basic information and any fields specific to the instrument. Then, only if the template leaves compliance parameters open, complete a "Compliance details" step; a template with a fixed compliance preset skips this step entirely, so its absence on your run is normal, not a fault. Finish on "Asset permissions", where you may add administrators or role holders beyond yourself.
Adding no one there is a valid choice. The final summary folds its Permissions card away entirely when you assign no one beyond the default deployer, rather than showing an empty one, so its absence on the summary screen does not mean your assignments were lost.
Review and deploy
"Review & deploy" checks that same combination for a collision live as you review it. It reads "Checking" while the check runs, "Your asset name, symbol, and decimals are available." once clear, "An asset with this name, symbol, and decimals already exists. Change any one of these to continue." on a collision, or "Unable to verify availability. Check your asset details and try again." if the check itself fails. Resolve any of these before you submit.
The "Unpause after creation" checkbox decides whether the token can transfer and operate immediately after deployment or starts paused, awaiting a separate unpause step later. If your template ships with no compliance controls, or is a manual-compliance template with no modules added, the summary shows that warning again under its own heading. Read it before you submit; the choice stops being yours to change the moment you do.
Confirm your wallet verification and submit. The Console does not make you wait on this same screen for the result. It hands off immediately to a full-screen deployment view with a live, step-by-step progress timeline. If the connection to that live feed drops, a banner says so while the deployment keeps running on the server behind it; wait rather than resubmit. If the connection never comes back and the stream ends without saying how the run finished, the view lands on a third screen, "Deployment Status Unknown", instead of success or failure. That screen carries no "Back to Wizard" button on purpose: the final deployment state is unknown, and returning to the wizard with your inputs in place could resubmit it. Use "Go to Activity" there to follow the deployment instead.
If your wallet runs short of gas mid-deployment, a funding prompt appears over the progress view instead of a failure, and deployment resumes once you fund it. On success, the screen confirms briefly, then takes you to the new token's own page. On failure, it names the problem, shows a copyable reference, and keeps every value you entered. Its "Back to Wizard" button returns you to "Review & deploy", not to a blank form or a specific flagged field, so you read the stated problem there and fix whatever it names, denomination-asset checks included, before resubmitting.
Troubleshooting
The issue action is missing
Signal: no "Issue new asset" entry appears anywhere, including the empty-state shortcuts on other asset-management pages. Cause: your account lacks token-create permission for the active organisation. Fix: ask an organisation administrator to grant it, then reload. A direct link to the wizard also redirects you away for the same reason.
The template you need is not listed
Signal: the first step lists fewer templates than the instrument templates catalog holds, or shows "No instrument templates are published". Cause: your organisation has not published the template, or has hidden it from the asset designer. Only Equity, Bond, and Stablecoin start published. Fix: with the Admin, System manager, or Asset designer role, follow the link under the list, or open "Asset design", then "Instrument templates", and publish the template. Without that role, ask an asset designer or administrator to publish it. Then reopen "Issue new asset".
Your saved template is no longer available
Signal: a resumed session shows "Your saved template is no longer available. Pick another one." and the continue button is unavailable. Cause: the template you picked earlier was unpublished, hidden, or deleted after you saved your progress. Fix: pick another template, or have the earlier one published again and reselect it.
A template cannot be selected
Signal: the template's card is disabled and carries a "Prerequisite setup needed" badge. Cause: the template pays fees, yield, or a maturity redemption in a denomination asset your organisation has not registered yet. Fix: use the card's own "Create a token" or "Register an existing token" button, whichever fits; both take you straight to that flow instead of leaving you to find it yourself. Once the asset exists in your organisation, return to "Issue new asset" and the card is enabled.
Review & deploy reports the name, symbol, or decimals already exists
Signal: "An asset with this name, symbol, and decimals already exists. Change any one of these to continue." Cause: an asset already deployed in this organisation carries the same three values; the Console treats the combination, not the name alone, as the identity it checks. Fix: use an approved name and symbol that distinguish the asset. Do not change decimals only to bypass the check: decimals define the token's precision.
Deployment fails after submission
Signal: the progress view ends on "Deployment Failed" with a stated problem and a copyable reference. Cause: several are possible. One worth knowing: the denomination-asset requirement is checked again, independently, against the live chain contract at submit time, so a token that looked eligible earlier can still fail here if its on-chain metadata cannot be read. Other causes surface as a plain chain-level error. Fix: read the stated problem, then select "Back to Wizard". Your entries remain in "Review & deploy". The error does not identify a specific field. Check the denomination asset, compliance modules, and permissions against its message. Copy the reference before contacting support for anything else.
The live progress view says it is reconnecting
Signal: a reconnecting banner appears over a progress list that has stopped updating. Cause: the live connection to the deployment stream dropped, but the deployment itself keeps running on the server behind it. Fix: wait; do not resubmit or navigate away. If the connection recovers, the timeline picks up where it left off. If it does not, the view moves on its own to the "Deployment Status Unknown" screen described below rather than staying stuck on the banner.
A deployment ends with no result
Signal: the progress view ends on "Deployment Status Unknown" instead of success or "Deployment Failed", with no "Back to Wizard" button. Cause: the connection to the deployment stream ended before it reported how the run finished; the final deployment state is unknown. Fix: do not resubmit. Use "Go to Activity" to follow it from there; the wizard button is missing on purpose, since returning with your inputs still in place could resubmit a token that is already being deployed.
A funding prompt appears mid-deployment
Signal: a dialog asking you to fund a wallet appears over the progress view instead of a failure. Cause: the account funding the deployment ran short of gas partway through. Fix: fund the wallet as prompted. Deployment resumes automatically once it detects the funds, while its funding window remains open. Check the operation status if funding arrives after a timeout.
Frequently asked questions
If I navigate away partway through, do I lose my progress?
It depends on where you go. Moving between wizard steps, or reloading the page, is always safe: your entries live in that browser tab's session storage and reappear when you return. Closing the tab, or opening the wizard in a new one, starts a fresh session instead, since session storage does not carry across tabs.
Leaving the asset designer for another part of the Console is different. The Console asks you to confirm the exit first, and confirming clears your entries for good, the same way a completed deployment does. Stay inside the wizard's own pages and your progress survives; confirm a leave prompt and it does not.
The Console offers no way to hand a partially configured asset to someone else; each person who wants to pick up where you left off starts their own attempt.
None of the available templates fit. Where do I create a new one?
Not on this page. "Issue new asset" only deploys from templates your organisation has published; creating or publishing one is a separate flow that lives with template design, not with deployment. Instrument templates covers that flow, reachable from the Console sidebar's "Asset design" section. Check there first for a DALP Library template that fits and is still unpublished. Once a template is published, it appears in this wizard's first step alongside the others; nothing else on this page makes it available.
Can I add or remove role holders after the asset deploys?
Yes, but not from this wizard. Once deployment succeeds, role assignments move to the deployed token's own page, which carries a dedicated permissions view for adding or removing role holders going forward. This wizard's "Asset permissions" step only sets who holds a role at the moment of deployment; skipping someone here is not a lasting mistake as long as your organisation can still grant them access afterward from the token's own page.
If I leave the token paused, can I unpause it later?
Yes. The Console always grants the wallet that deploys the token the emergency role that "Unpause token" requires, whether or not "Unpause after creation" is checked; that checkbox only decides whether the token starts paused, not who can unpause it afterward. You do not need to add yourself on "Asset permissions" for this to work.
"Unpause token" sits as its own control on the deployed token's own management menu. If you want a wallet other than the one that deployed the token to hold that role too, grant it emergency explicitly on "Asset permissions" during the wizard, or from the token's own permissions view once it exists.