Issue from the templates your organisation approved, and answer who held a security on a record date. Your issuers see only the templates product control has published, from a library that grows by twelve, including two sukuk. The holder register comes from the token's own balance history, reconciled against total supply before anyone sends it.
The template fixes how an instrument behaves, and the token's balance history answers who held it
An asset designer decides which templates issuers may use. Every holder list at a record block is checked against total supply before anyone can deliver it.
- Templates
- Thirty-six, in seven asset classes
- New in 3.2
- Twelve, including two sukuk
- Register exports
- CSV, XLSX, PDF and a registrar file
- Look-through
- Beneficial owners behind a nominee
Before and after
Before 3.2: each issuance was configured by hand, so two bonds from the same desk could carry different features and compliance settings. When the registrar, the transfer agent or the regulator asked who held a security on the record date, the operations team rebuilt the answer from exports and reconciled it by hand, and a custodian's omnibus wallet showed as one holder with no view of the investors behind it.
With 3.2: issuers choose only from the templates your organisation has published, so every instrument of one kind starts with the same behaviour. The holder register reads balances at a record block from the token's history, refuses to deliver a list that does not add up to total supply, exports it as a registrar file and looks through a nominee wallet to the owners its nominee declared.
Published templates fix how an instrument behaves, and its balance history feeds the holder register, registrar file and beneficial-owner look-through.
Issue sukuk, venture and digital asset instruments from the catalogue
The DALP Library grows to thirty-six templates in seven asset classes, and each one is a configuration of contracts the platform already runs. The twelve new templates start with the Ijara and Murabaha sukuk under a Shari'ah and AAOIFI compliance policy, a government security for sovereign, agency and sub-sovereign paper, and a spot commodity. A new Digital assets class holds a tokenised virtual asset and a custody receipt. Venture financing gets a SAFE, a warrant and the convertible equity they convert into. A controlling class share and an economic class share form a two-class equity that issuers pick as one structure, and a share-class mirror serves funds whose register a transfer agent or administrator keeps. An Islamic bank that wants to tokenise an Ijara sukuk starts from a template that already carries the sukuk structure and its compliance policy, instead of commissioning a custom contract. A template sets the instrument's behaviour on the token, and the legal documentation and the Shari'ah board's opinion stay with your institution.
Your asset team browses the library of published instrument templates.
Offer issuers only the templates your organisation approved
Issuers can choose only from the templates your organisation has published. Common Equity, Corporate Bond and Fiat-Backed Stablecoin are published from the start, and every other DALP Library template stays unpublished until you publish it. An asset designer who wants a house bond opens Corporate Bond in the DALP Library, chooses Duplicate template, picks the token features the house standard needs on the “Token features” tab, and marks which settings are fixed and which the issuer fills in at issuance. The draft cannot be published while a token feature is not configured, and once it is published, every bond the desk issues from it carries the same features and compliance policy. A DALP Library template cannot be edited, so a change to one starts with a copy of it, and where the operator allows the seven original asset families, the asset types DALP offered before templates, users can still create those without a template.
Answer who held the security on a record date
An operator can set the holders list to a past day, back to when the asset's balance history began, and read the holders as they stood at the end of it. The current view shows available, frozen and locked balances separately. Export holder register builds the shareholder list at a record block: each holder with their registered identity, country, units and share of supply, sorted by holding. Its summary shows whether the holders add up to total supply and says not to send the list when they do not, and “Deliver to issuer” stores CSV, XLSX and PDF editions for the issuer's owners and admins, who get an email with a link and never the holder data itself. A company secretary preparing a dividend reads the list at the record date and sends a file the platform has already reconciled against supply. The past view shows only the holder, the balance and the share. The shareholder list, the registrar file and the beneficial-owner register work only once your operator switches regulatory reporting on, and an asset without the Historical balances feature, or one that already had supply when the feature was attached, cannot produce a list at all.
Reconcile with the registrar and see the owners behind a nominee
Registrar file… downloads the register at the record block as one row per wallet, with its identity reference, country and quantity, and “Reconcile registrar file” takes the registrar's own CSV back and marks each wallet as matched, mismatched, missing on chain or missing in the register. A nominee, custodian or broker declares the beneficial owners behind one of its wallets with “Declare beneficial owners”, in the Console or through the API, and the platform keeps the declaration only when its units add up to the wallet's balance at that block. “Register by beneficial owner” then reads the register looked through to those owners, with each read written to the audit trail, and the owners' names and ID numbers are encrypted in the platform database and never written on chain. A CSD can see the investors inside a custodian's omnibus wallet, and an issuer can tell each of them their share of a dividend, while the dividend itself is still paid to the nominee as one payment. Shareholder lists are also delivered on their own after a call auction settles, when the last trading day of a month closes and as a flagged correction after a bust, and those three follow trading on a DALP venue. The registrar file uses DALP's one built-in layout, so a registrar that needs another format needs that layout added.
Give holders the documents that concern them
Post a document once and every investor who holds the asset reads it from the asset page. Each document is “Public”, Holders only or “Restricted”, terms documents are always public, and only holders of the asset's governance role can add or change them. An issuer posts an annual report as Holders only, and every holder reads the same file, with its integrity check and its download, instead of receiving it by email. A holder sees the public documents and those marked Holders only, and never a restricted one. The Console and the Investor portal both preview PDF, Word, Excel, CSV and image files in the browser and offer every other file as a download.
Upgrading
Assets you have already issued keep working as before, and none of this changes their configuration. An asset gets the Historical balances feature from its template at issuance, so check an existing asset's Features tab before you rely on its holder register. Issuance from a template now needs that template to be published, so an organisation that issues from a DALP Library template other than the three published from the start publishes it first, as Template publication describes for integrations. Templates whose features are new in 3.2, such as the share-class mirror and the custody receipt, need the organisation to run System updates first. Creating a token from a template whose feature has no factory on the system is refused before anything is signed, with HTTP 409 TOKEN_ (DALP-207901), and Issue asset marks the template as needing a feature factory. Creating an asset in one of the seven original asset families has been off since 3.1.19 and stays off, and an operator who still needs it decides that before the upgrade, as Upgrade a deployment to DALP 3.2 describes. Existing assets in those families keep minting, transferring and reporting. The holder register exports, the registrar file and the beneficial-owner register come with regulatory reporting, which stays off until your operator switches it on, as Upgrade a deployment to DALP 3.2 describes.
Why it matters
- Banks: every bond, deposit or fund your desks issue from the catalogue starts from a template product control approved, with the same features and compliance policy each time.
- Exchanges, CSDs and market infrastructures: the register at a record date reconciles against supply and against the registrar's file, and looks through custodian wallets to the owners behind them.
- Regulators: A shareholder list names the record block it was read at and states whether it adds up to total supply.
- Partners: on a mirrored share class, a transfer agent or administrator keeps the legal register and moves units on chain only through booked movements it records.