Design each instrument from a reviewed template, enforce its compliance policy on every ordinary transfer, and keep signing in the custody you already run.
A regulated institution spends most of an instrument's life servicing it after issue. DALP 3.0 starts each new instrument from templates your teams have reviewed and puts issuer-signed prices on the token. It keeps signing in the custody you already run and records every transaction step, so a stalled write resumes instead of going missing.
Read Breaking changes and migration before upgrading.
Configure instruments and compliance
The centre of 3.0 is asset design.
- Start every new instrument from a reviewed template. Twenty-four library templates across six asset classes give the issuer a reviewed design and leave only the terms of the issue to fill in.
- Write a compliance policy once and reuse it. Your compliance team publishes identity, country, limit and approval rules as a template, and each new token that uses it copies the rules and checks them on every ordinary transfer through ERC-3643. ERC-3643 is the open Ethereum standard that requires a verified on-chain identity before a transfer settles.
- Enforce verified KYC at transfer, keep documents off chain. The asset checks a verified on-chain claim, and the documents behind it stay off-chain.
- Run fees, coupons, redemption and conversion on the token. Fee, yield, redemption and conversion features attach to the live token and record what they do for each holder.
- Price each token from a feed a trusted issuer signs. Issuer-signed prices and values reach the chain, one feed per token.
A platform built to run it
3.0 also changes how the platform signs, records and tracks transactions.
- Let operators act without funding their own gas. Operators work through smart wallets, and a paymaster pays the gas for each operation the platform authorises.
- Keep signing inside your own custody. DFNS, Fireblocks, Ripple Custody or Luna HSM keep the keys and their approval policy, local signing remains the fifth option, and DALP builds and tracks every transaction to confirmation.
- Resume a stalled transaction from its last recorded step. Every write carries a recorded state, so a pending approval or a network timeout resumes from where it stopped.
- Read your on-chain history as business records. Ledger Data decodes each block into holdings, transfers, fees and redemptions, and rolls back and replays recent blocks when a chain reorganisation replaces them.
- Pay less gas on identity, compliance and proxy checks. The 3.0 contract versions read storage fewer times and enforce the same rules, and an existing system gets them through System updates.
Operate it from one place
The release also makes the platform observable and reachable.
- See platform health in one verdict. Platform status brings health into the Console in terms an operator can act on.
- Receive signed events instead of polling the API. DALP posts signed identity registration and role events to your systems and records every delivery attempt.
- Automate DALP operations from the CLI, SDK and MCP. The SDK, the CLI and its MCP server give scripts and AI agents the CLI's operations with typed errors. MCP, the Model Context Protocol, is an open standard that lets an agent discover and call those operations.
- Filter, page and track settlement through the v2 API. Integrators get filtering, sorting, idempotency keys and control over whether a write waits for its result, while the v1 API keeps its request and response shapes.
- Upgrade your on-chain components in one confirmed run. The Console's System updates page lists every component that is behind before one run moves them all.
- Answer a security review with enforced controls. Authentication, key scopes, role checks, wallet codes and deployment controls are each enforced and documented.
- Look up API and error references generated from the platform. An error code your integration receives leads to its cause and fix under the same code and message, and each part of the platform has one name across the docs.
Breaking changes and migration
- Run System updates after the platform moves. Open System updates and run Upgrade all so your on-chain components and the features on your tokens pick up the 3.0 behaviour. Upgrade your on-chain components in one confirmed run covers the run.
- Role checks apply to endpoints that had none. A key or account that relied on an operation with no check at the API layer receives FORBIDDEN after the upgrade, so review grants before you upgrade.
- Price inputs move to per-token feeds. An asset that priced from a base-price claim keeps reading that claim after the upgrade, because claim fallback is on by default. That price stays static and gets no freshness check, and the Platform API reads prices from feeds only, so such an asset shows no feed price there until it has a feed. Create a feed for each token to receive signed, freshness-checked prices. A wallet holding the Feeds manager role can then turn the fallback off with a direct call to the price resolver contract. Price each token from a feed a trusted issuer signs covers the feeds.
- Platform status reads each panel from its own route. The panels live under
/api/v2/platform-status/:data-freshness,transactions,platform-api,workflowsandstat-cards, withhistoryas a separate read. The combined/read is deprecated and returnsapi/ v2/ platform- status/ snapshot DeprecationandSunsetheaders, so move clients to the per-panel routes. - Ledger Data builds its records on first start. After the upgrade, Ledger Data builds its records from each network's history, so the first start takes longer on a long history.
- The v1 API keeps its shapes in 3.0. v1 routes keep their request and response shapes, and new capabilities land on v2.
Smaller updates
- Hide or unhide asset classes and instrument templates in Asset Designer, including per organisation, so each team sees what it issues.
- Search currencies by country and currency name.
- Resize the sidebar by dragging, with snap-to-collapse and a toggle shortcut.
- Real estate tokens can burn supply in their new contract version, and tokens already issued gain burn once they are upgraded to it.
- An XvP settlement swaps an asset for payment once every party approves. A settlement with a leg on another network also waits for its hashlock secret, which must be revealed before the cutoff date, and that leg settles as its own transaction on the other network, so the two legs are not one transaction.