Skip to main content

Write a compliance policy once and reuse it

Your compliance team publishes a policy template once, and each new token copies it on-chain and checks it on every ordinary transfer.

Your compliance team writes the policy once, and every new instrument that uses it starts with the same checks on its token. When the policy lives in a document and the controls are rebuilt by hand for each asset, a country added to the policy can be missed on one token and nobody sees it until a transfer clears that should not have. DALP 3.0 turns the policy into a template the asset team picks in Asset Designer.

A policy template becomes each new token's own on-chain compliance, checked on every ordinary transfer

A template bundles identity checks, a country allow list, investor or raise limits and transfer approvals. The token runs those rules itself, so a transfer that fails one does not settle.

Built-in templates
Nine regulatory regimes
Applied
Copied to each new token
Global controls
Apply to every bound token
Rejections
Typed reasons

Before and after

Before 3.0: the compliance team kept the policy in a document, and the asset team rebuilt the controls for each new token. A country added to the policy could be missed on one asset, a cap updated in one place and not another, and the only way to find out was to compare each token's settings against the document.

With 3.0: A Compliance manager builds the policy as a template in “Policy templates” and publishes it. The asset team picks it in Asset Designer, the token deploys with its own copy of the rules, and global controls set once at platform level apply to every token as well.

From a draft policy template to the check on each ordinary transfer.A Compliance manager drafts a policy template with identity, country and limit rules and publishes it. In Asset Designer the Asset manager picks it, and the new token receives its own copy of the modules at creation. Each ordinary transfer is checked on-chain against the token's rules and then against the global controls that apply to every bound token. A Custodian's forced transfer or wallet recovery, the compliance bypass list and a fee-recipient exemption skip the check, and the token's Governance role can install or remove modules later.From a draft policy template to the check on each ordinary transfer.A Compliance manager drafts a policy template with identity, country and limit rules and publishes it. In Asset Designer the Asset manager picks it, and the new token receives its own copy of the modules at creation. Each ordinary transfer is checked on-chain against the token's rules and then against the global controls that apply to every bound token. A Custodian's forced transfer or wallet recovery, the compliance bypass list and a fee-recipient exemption skip the check, and the token's Governance role can install or remove modules later.

A published policy template gives each new token its own copy of the rules, and each ordinary transfer is checked against them and the global controls.

Let the asset team apply a policy the compliance team owns

The compliance team owns the policy, and the asset team applies it without making compliance decisions. A Compliance officer opens “Policy templates”, picks the DALP Library template MAS Singapore - Capital Markets and chooses Duplicate template. The copy holds four controls: identity verification, a Singapore-only country allow list, a limit of 50 investors and a 180-day holding period. The officer adds the claim topics the programme requires and chooses “Publish template”, which the Console asks the officer to confirm because it cannot be undone. An Asset manager creating a new fund reaches “Select compliance template”, picks that policy, and the fund deploys with those four modules installed on its token. A transfer to an investor whose verified identity sits outside Singapore fails the allow list and does not settle.

Compliance officers browse the published policy templates and the jurisdiction each covers.

Only an administrator or a Compliance manager can create or publish a policy template, while an Asset manager can read and apply one. Two tokens created from the same published version start with identical rules. Each token keeps the copy it received at creation, so publishing a changed template does not change tokens already issued, and the token's Governance role can install or remove modules later.

Start from nine regulatory templates

The DALP Library ships nine current templates. Each includes identity verification, which requires a registered identity until your team adds the claim topics the programme needs.

Template
What it sets
MiCA EU Standard
The 27 EU countries, a capital raise limit of 8,000,000 in the base currency per rolling 365 days
Reg D 506(b) - Private Placement
United States only, at most 2,000 investors
Reg D 506(c) - Accredited Only
United States only, transfer approvals valid for one day, accreditation once you add its claim topic
Reg CF - Crowdfunding
United States only, a capital raise limit of 5,000,000 in the base currency per rolling 365 days
UK FCA - Securities
United Kingdom only, at most 150 investors
MAS Singapore - Capital Markets
Singapore only, at most 50 investors, a 180-day holding period
Japan FSA - Crypto Assets
Japan only, transfer approvals valid for seven days
Australia ASIC + AUSTRAC - Digital Assets
Australia only, transfer approvals valid for seven days
UAE VARA + ADGM/DIFC - Virtual Assets
United Arab Emirates only, transfer approvals valid for seven days

The library templates name no approval authority, so on a template with transfer approvals nobody can approve a transfer until your team names one. Library templates are read-only, so your team duplicates one and sets the trusted issuers, claim topics, approval authorities and limits its programme needs. Your counsel starts from a configuration that already reflects the regime instead of an empty form. The Reg D 506(b) template caps total holders and does not count non-accredited purchasers separately. A template configures platform controls, and choosing one does not make an offering compliant with the regime it is named after.

Set a rule once for every token on the platform

Some rules apply across every instrument. Global controls in Settings apply compliance controls at platform level, and every token bound to the platform checks them after its own rules. A Compliance manager who must keep one country out of the whole book sets that rule once there, instead of editing each token's policy. Each module can also be scoped to the cases it governs, by country code, by identity claim topic or both.

A global control reaches tokens issued before it was set as well as new ones, which a per-token copy cannot do. Global controls apply to every bound token, so a rule meant for one programme belongs in that programme's template.

Read the exact reason a transfer was refused

When a mint or transfer fails compliance, the platform returns one of three typed reasons: the identity is not registered, the identity is not verified, or a named module blocked the operation. It says whether the sender or the recipient failed, and an unverified identity comes back with the claim topics that are missing, revoked or expired. An operator sees that the recipient lacks a current KYC claim and asks the verification issuer for it. Integrations read the same reasons, and each template with its modules, jurisdictions and draft or published status, through the Platform API and the CLI.

The reason tells your team what failed, and fixing it, such as issuing the missing claim, stays with the verification issuer.

Name every path that skips the check

Every module runs on-chain for each ordinary mint and transfer, and the paths around it are few and named. A Custodian's forced transfer or wallet recovery moves tokens without the transfer rules, by design. A transfer to an address on the compliance bypass list skips every module. The Compliance manager role maintains the list, and DALP's factories add the platform's own contracts to it when they deploy them. An approval authority can exempt a fee recipient from transfer approval, and the token's Governance role can remove a module. When a holder loses a wallet, a Custodian moves the balance to the new wallet, or, once an Identity manager has recorded the recovery, the new wallet claims it itself, and no module is consulted in either case.

A regulator who asks how a token could move outside its rules can be shown these paths, each tied to a role your institution grants. Who holds the Custodian, Identity manager, Governance and Compliance manager roles is therefore part of the policy.

Upgrading

Nothing to do. Tokens deployed before 3.0 keep their compliance modules unchanged. Choosing a template stays optional, because Asset Designer also accepts a manual configuration or no compliance at all, and it warns that the asset deploys without compliance controls. Templates built on the earlier module generation for older asset types carry the Legacy badge.

Why it matters

  • Banks: the compliance team owns the policy, the asset team applies it, and each token that uses it enforces it on every ordinary transfer.
  • Exchanges, CSDs and market infrastructures: A token arrives with its rules on-chain, and the active controls are readable through the API.
  • Regulators: the rules a token enforces sit on the token, and every path around them is a named role.

Next steps

Was this page helpful?