Instrument templates

Instrument templates help asset teams reuse the same issuance setup across assets. A template groups the asset class, deployable asset type, required token features, feature defaults, and metadata fields that the Asset Designer should collect during issuance.

Use instrument templates when you want repeatable setup for a family of assets, such as bonds with a maturity feature, stable-value instruments with required metadata, or organization-specific asset classes.

Template types

DALP uses templates at different points in asset setup:

These templates compose rather than replace each other. An instrument template handles the asset setup, token template settings handle token behavior, metadata fields handle asset-specific information, and a compliance template can be selected in the compliance step when the asset needs reusable policy controls.

Where templates fit

An instrument template does not issue an asset by itself. It defines reusable defaults and requirements that the Asset Designer applies when an operator creates an asset.

Template sources and statuses

The instrument template list separates templates by source and status:

The list page supports search, source filtering, status filtering, and asset-class filtering. Template cards show the template name, description, source, status, and any required feature badges.

Create a template

Open Platform settings → Templates → Instrument templates, then choose one of the creation modes:

• From existing copies an existing template's name, description, asset class, required token features, metadata schema, feature configuration, and base asset type into a new draft.
• From scratch starts a new draft where you select the asset class and configure the template manually.

When creating or editing a template draft, configure:

• Name and description so operators can pick the right template later.
• Asset class to connect the template to a managed asset category.
• Required features to attach token-level behavior such as maturity, yield, fees, conversion, or other installed token features.

After the template draft exists, use the template detail page to add metadata fields and adjust feature-specific settings before publishing it.

Template names must be unique within the organization. If a duplicate name is entered, DALP keeps the form open and shows an inline validation message.

Work with required features

Required features are shown as badges on template cards and as active features on the template detail page when the matching feature is available in the environment.

On the template detail page, users with template management permissions can:

• add available features,
• remove active features,
• adjust feature configuration,
• choose which configured feature settings remain editable in the Asset Designer.

Configurable feature settings are controlled per setting. For example, a template can keep a fee recipient fixed while allowing an operator to enter the fee value during asset creation. Settings that are not configurable stay on the template as defaults and do not appear as editable inputs in the Asset Designer.

During asset creation, configurable settings from the selected template are grouped by token feature. Each feature card has its own heading and can be expanded or collapsed independently, so operators can complete maturity, yield, fee, conversion, and metadata fields without mixing the controls together.

If a copied template references a feature that is not deployed in the current environment, DALP warns the operator while preparing the new draft instead of silently treating that draft as fully ready.

Define metadata fields

The Metadata tab appears when a template has metadata fields or when the current user can manage the template. Each metadata field has a field key, type, mutability, label, and optional constraints.

Supported metadata field types include text, number, date, enum, ISIN, and address fields. Required fields must be completed during asset creation. Fields marked immutable are locked on the issued asset after deployment; fields that are not immutable can still be managed through the supported metadata update flow, subject to permissions and governance controls.

Publish, duplicate, edit, and delete

Template actions are available from the template detail page.

DALP library templates are read-only. They can be duplicated when your organization needs a similar template with its own asset class, feature choices, or metadata fields.

How templates affect asset creation

When an operator selects a template in the Asset Designer:

• required feature badges explain which token behaviors are included,
• template-specific metadata fields are added to the details step,
• required metadata fields must be completed before the wizard continues,
• template defaults are applied for feature-specific settings,
• feature-specific fields are grouped into separate cards when the selected template includes more than one configurable feature,
• the selected template determines which asset class and base asset behavior the deployed asset uses.

Some required token features also need another token before the operator can select the template. Templates that use maturity redemption, fixed treasury yield, or external transaction fee behaviour need an ERC-20 token in the tenant. Templates that use conversion need an equity-class target token.

Templates can also have feature dependencies:

• Include conversion when a template includes conversion-minter.
• The minter must be paired with the conversion behaviour it serves.

If a required token is missing, the Asset Designer disables the affected template and shows the missing token type. The operator can create or register the required token, then return to the wizard and select the template after the token is available.

Feature dependencies belong to the template configuration itself. If a template feature dependency is missing, update the template's feature selection before publishing or updating the template.

Examples

Use these examples as patterns for how template parts affect issuance:

• A bond-style instrument template can require maturity redemption and fixed treasury yield features. During asset creation, the operator sees those token behaviors as required feature badges and completes any configurable settings before deployment.
• A real-world asset template can require metadata such as an ISIN, valuation date, address, or reporting category. Required metadata fields block wizard progress until completed. Immutable metadata fields are locked on the issued asset, while restricted-mutable fields can still follow the supported metadata update flow.
• A compliance template can group reusable controls such as country lists, identity checks, holding limits, and transfer approvals. In the compliance step, the Asset Designer filters published templates by the asset context and carries selected controls into the asset's initial compliance setup.
• Operators can also skip a compliance template and configure compliance modules manually when the asset needs one-off policy setup instead of a reusable template.

For the end-to-end issuance flow, see Create asset. For the conceptual model behind templates, see Asset model.