System templates

DALP ships 24 built-in templates that the Asset Designer offers when an operator creates a new asset. Each one selects a base asset type, an asset class, a set of required token features, and a metadata schema for the fields the operator fills in. This catalog maps every template to those choices so operators can pick the closest fit before opening the Asset Designer.

Custom organisation-owned templates extend the catalog without changing the system templates. For the authoring path, see Custom template authoring. For how features compose, see Feature constraints.

System templates and system asset classes are read-only, with one exception: you can hide or show them per organization to keep the Asset Designer focused on the products you offer. Hiding does not modify or remove the template. It only removes the template from your organization's pickers, and you can reverse it at any time. See Show or hide templates and asset classes.

How to use the catalog

The Asset Designer reads the selected template and applies its required features together with operator inputs from the wizard. It then validates the combination against the dependency and incompatibility rules before deployment. Pick the template whose features and asset class match the instrument shape. Do not override the required-feature list unless the asset deliberately diverges from the template intent.

Fixed income (asset class fixed-income)

Seven templates target debt instruments backed by the bond base asset type.

Use system-treasury-bill or system-commercial-paper when the instrument is a discount zero-coupon at issue and pays at maturity. Choose system-convertible-note when conversion to a target equity is in scope; the conversion-minter dependency is required for the conversion flow. system-syndicated-loan suits agent-bank-funded periodic yield against a facility id. Pick system-green-bond when use-of-proceeds reporting is part of the operating model.

Equity (asset class equity)

Three templates cover share-like instruments backed by the equity base asset type.

system-equity covers voting common shares. system-preferred-equity drops voting-power because preferred classes are often non-voting. If the preferred class votes, override the required-feature list and document the decision in the template description. system-employee-equity-award adds voting-power because employee awards frequently carry voting once vested.

Funds (asset class funds)

Four templates cover pooled investment vehicles backed by the fund base asset type. See Funds use case for the operating model.

system-fund collects an on-chain transaction fee against subscriptions and redemptions. system-etf switches to transaction-fee-accounting, which records the fee without collecting it on chain. Operators or the administrator settle accrued fees off-chain on the published schedule. system-money-market-fund adds fixed-treasury-yield because short-duration cash-equivalent funds typically distribute the treasury yield to holders. system-private-equity-fund keeps voting-power for limited-partner-style governance. It drops transaction-fee because subscriptions are typically capital-call events scheduled outside the token transfer path.

Cash and cash equivalents (asset class cash)

Three templates cover bank-deposit and stable-value instruments.

system-stablecoin is the minimal template: the operating model expects collateral attestation through compliance modules rather than a yield feature on the token. system-deposit adds fixed-treasury-yield for demand or term deposits that pay interest. system-certificate-of-deposit adds maturity-redemption for term-CD instruments that pay face at a defined date.

Real assets (asset class real-assets)

Four templates cover physically or environmentally backed tokens.

system-precious-metal is minimal because the asset reads weight, purity, and custody facts from the metadata schema, not from token features. Use the precious metals walkthrough when you need the issuance steps and backing-evidence split for a gold, silver, platinum, or palladium programme. system-real-estate adds voting-power for fractional-ownership governance and aum-fee for property-management accrual. system-carbon-credit is conversion-based because retired credits convert into a retirement token rather than redeeming through maturity. system-tokenized-art adds voting-power for fractional decisions about the underlying piece.

Tokens from every real-assets template support burn, so a supply manager can permanently remove units from circulation: cancel a fractional real-estate holding, retire a credit, or correct an issuance. Burning follows the same rules as any other asset. It needs the supply management role, the asset must not be paused, and it destroys supply rather than transferring it. See Burn assets for the console steps, batch limits, and frozen-balance handling.

Structured products (asset class structured)

Three templates target structured-note and asset-backed instruments backed by the bond base asset type.

system-principal-protected-note pairs maturity-redemption with fixed-treasury-yield so principal returns at maturity with coupon accrual along the way. system-autocallable-note drops the yield feature because autocallable returns are payoff-shape-dependent rather than periodic. The operator records the payoff terms in the template metadata. system-asset-backed-token is the most feature-dense entry: it composes treasury yield with fee accounting and an external transaction fee to model securitised pools where the fee is paid in a separate denomination asset.

Choose between similar templates

When the catalog does not fit

If none of the built-in templates match the intended instrument, author an organisation-owned template instead of overriding the required-feature list on a system template. Organisation-defined templates preserve the catalog as a stable reference and give your override an identifier the auditor can trace. See Custom template authoring.

Read next

• Custom template authoring for the tutorial that walks an operator from blank to a published organisation-owned template.
• Create asset for the Asset Designer entry path that consumes a chosen template.
• Feature constraints for the dependency, incompatibility, and order-of-application rules the Asset Designer enforces.
• Token features for the per-feature architecture references the catalog above links into.