Asset Designer

Open the asset designer

Click Asset designer in the sidebar under Asset management to open the wizard. The wizard runs as a routed flow under /asset-designer. Each step has its own URL, so browser Back and Forward move between steps instead of leaving the flow. If you refresh the page while creating an asset, the wizard restores your in-progress values and returns you to the current step in the same browser session.

If you navigate away from /asset-designer after making any progress (choosing an asset class, selecting a template, entering a name or symbol, picking a compliance template, or setting permissions), the platform asks you to confirm before discarding the wizard state. A successful deployment, an in-app leave you confirm, or sign-out clears the saved state.

Select asset class

Choose the asset class that matches your security type. DALP shows only classes that have at least one usable published template. Choosing a different class clears the previous template selection, template-specific metadata, and feature inputs so stale values do not carry into the next asset.

Select instrument template

Choose the published instrument template for the asset you want to create. The wizard shows the required features and compliance options attached to each available template. Required features are token behaviors the selected template attaches during deployment, not optional choices you remove during issuance.

If a template needs a prerequisite token that is not available in your tenant, the template card stays disabled and names the missing prerequisite. Use the card button to create the needed token or register an existing external token, then return to the wizard and select the template after the prerequisite is available.

Review template-required features

Instrument templates can include required features. When a template has required features, the Asset Designer shows them as badges during template selection. The deployed asset inherits those token-level behaviors from the selected template, then asks for additional inputs only for the badges that need configuration.

Template-specific fields and defaults

Selecting an instrument template can prefill feature settings and metadata values in the wizard. The Asset Designer clears feature-specific values from the previous selection before applying the new template, so switching templates does not carry old maturity, yield, fee, or conversion inputs into the next asset.

Templates can also add metadata fields to the follow-up details step. These fields can be text, number, date, enum, ISIN, or address inputs. Required metadata fields must be filled before the wizard continues.

Template defaults are applied when you select the template.

For required-feature badges, fields that are fixed by the template can remain hidden while still being submitted with the asset configuration.

Template feature settings that are not part of the template's required features can seed the wizard, but they are not submitted as standalone feature configurations.

Prerequisite tokens

Some required features need an existing token before you can select the template. The table below lists which token each feature checks for and what the wizard shows when it is missing.

The prerequisite check looks at tokens and registered external tokens in the tenant. It only decides whether the template can be picked. The contract and deployment workflow still validate the selected token addresses and feature settings when you submit the asset.

Self-contained required features

These badges do not add a follow-up configuration step from the required-feature badge itself. Use the token feature catalog for the canonical behavior reference.

Current self-contained badges include Historical Balances, Voting Power, Permit, Transaction Fee, Transaction Fee Accounting, Fixed Treasury Yield, and Conversion Minter. Transaction-fee badges only create non-zero fee behavior when the template supplies fee settings; Fixed Treasury Yield only creates a configured yield schedule when the template supplies yield settings.

Configurable required features

These badges show follow-up inputs in the Asset Designer after template selection. Use the token feature catalog for canonical feature behavior; this table only lists the extra guided inputs.

Configure asset basics

Enter the core asset properties. The Asset Designer shows live character counters below text inputs and checks these values before you can continue, so use values that describe the exact instrument you intend to deploy.

When the symbol field is empty, the wizard suggests a symbol from the asset name. A one-word name uses the first five letters, a two-word name combines the beginning of both words, and longer names use an acronym. You can replace the suggestion before continuing.

Most asset classes also take a base price and a pricing currency here. Use the currency picker next to the base price to choose the fiat currency the price is quoted in. Type in the search box to narrow the list. The picker matches by ISO 4217 code, currency name, and country name, so you can find any option without knowing its code. Searching Malaysia or Malaysian Ringgit, for example, finds MYR. Matching ignores case and accents, and each entry is labelled Currency name (CODE) so you can confirm the right one before you select it. The picker offers a curated set rather than the full ISO 4217 list.

Maturity-bearing assets such as bonds are priced against their denomination asset, so they do not show the base price and currency fields in this step.

As you fill in the basics, DALP checks whether the asset is available and shows the result inline.

Asset uniqueness and the availability status

Within your organization, an asset is identified by the combination of its asset type, name, symbol, and decimals. You can deploy only one for any single combination, so reusing all four values points back to one you already created. Vary any single value and you describe a distinct asset. The same name, symbol, and decimals under a different asset type is also distinct, not a duplicate.

The availability status reflects that rule against the values you have entered. You can continue to the next step only when the status is Available. The Next button stays disabled while the status is Unavailable or Cannot verify, and the route guard keeps the basics step incomplete until the check passes.

Changing the type, name, symbol, or decimals clears the previous result and starts a new check, and the same values feed the asset summary you review before deployment.

DALP also shows an inline duplicate-asset warning while you edit the basics whenever the name, symbol, and decimals already match one of your organization's assets of the same type. The warning is advisory and names the existing asset. It does not block the Next button. A duplicate that reaches deployment is stopped with a message naming the existing asset, and your inputs are kept. Return to this step, change the name, symbol, or number of decimals, and create the asset again.

Configure asset details

Complete the template-specific fields shown by the wizard. DALP inserts the details step only when the selected template exposes configurable required-feature inputs or metadata fields. Templates without input fields skip directly to pricing.

For a precious metal asset, this step records the metal metadata and terms: metal type, purity grade, vault location, custodian (all three are optional), weight unit, and weight per token. Price currency and base price are part of the asset basics. Use these fields to describe the digital metal program; keep assay certificates, storage receipts, insurance documents, and other backing evidence in your external operating records or token document uploads.

Choose compliance controls

The compliance step starts from a policy template rather than a blank list of modules. Under "Choose a Policy template", the wizard shows the published policy templates available to your organization, each labelled DALP Library or Organisation and tagged with its jurisdictions and the number of controls it carries. Selecting a template applies its full set of controls to the asset in one step, so most operators do not configure modules by hand.

You have three ways to set compliance here:

• Pick a policy template to apply a curated set of controls for a jurisdiction or program. Policy templates keep asset configurations consistent and match the controls your compliance team has already approved.
• Select No compliance to deploy the asset with no controls. DALP warns that holders and transfers will not be screened. You can still install compliance modules later from the asset's Compliance tab.
• Turn on Advanced configuration to build the control set yourself. The toggle reveals an enabled-controls list and an available-controls list so you can add or remove individual modules.

Individual compliance controls

Advanced configuration and the policy templates draw from the same set of on-chain controls. Each control is enforced automatically for every transfer.

When you apply a policy template, the asset must submit every control the template declares. DALP rejects the deployment when those controls are missing from the final configuration, or when a country allow list has no countries selected, because an empty allow list would block every transfer.

For more details on compliance modules, see the compliance overview.

Set initial asset permissions

Confirm which wallets should receive asset-level roles when DALP deploys the token. The wizard keeps your connected wallet in the permission list with the Admin, Governance, Supply Management, and Emergency roles, and you cannot remove your own entry. Together these let you run the first operating steps yourself after deployment: Emergency authorizes unpausing the asset, and Supply Management authorizes minting the first supply.

Use Add permission to grant another wallet one or more asset roles before deployment. Current asset-level roles include Admin, Custodian, Emergency, Funds Manager, Governance, Sale Admin, and Supply Management. Add only the roles each wallet needs for its first operating step.

Review and deploy

Review the selected template, asset details, compliance controls, and initial permissions on the summary page. The summary also lists the token-feature settings you configured, grouped under the instrument template, so you can confirm them at the last checkpoint before the transaction goes out.

For a convertible note, the summary includes conversion settings: the target token, the denomination asset, and the discount as a percentage. Confirm these before proceeding. They decide how holdings convert and are the highest-risk part of the configuration.

When ready, click Deploy and authenticate with your PIN or OTP to submit the transaction. After authentication, the platform broadcasts the deployment transaction to the network.

After you authenticate, DALP shows a live deployment progress screen. Each stage appears as a step in a timeline that updates in real time: deploying the token contract, granting permissions, issuing claims, and, when they apply, submitting the initial price feed and unpausing the asset. Steps that do not apply to your asset are not shown. Keep this screen open until it finishes. When every step completes, DALP takes you straight to your new asset's detail page.

Funding the wallet during deployment

On a network where gas is not free, deployment can stop and wait when the wallet you deploy from does not hold enough of the network's gas token to cover the transactions. Instead of failing, the progress screen shows a funding request. The request names the wallet address to top up, the network to fund it on, the smallest amount that clears the shortfall, and a recommended amount that also covers the rest of the deployment. The recommended amount accounts for every transaction the deployment still has to send, so funding it once is enough to finish in a single pass.

Send the gas token to the named wallet on that network. DALP watches the wallet and continues on its own once the balance is enough, with no need to resubmit or start the wizard over. You can dismiss the funding request to a small status indicator to keep the full progress timeline in view; reopen it any time to see the address and amounts again. A small over-send is harmless.

If a stage fails, the screen names the step that failed and shows the error with a reference you can copy. From there you return to the wizard with every input still populated, so you can adjust the configuration and submit again.