Skip to main content

DALP 3.0: design your own digital asset

Issue from reviewed instrument and compliance templates, sign in your own custody and resume every transaction from its last recorded step.

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.

A platform built to run it

3.0 also changes how the platform signs, records and tracks transactions.

Operate it from one place

The release also makes the platform observable and reachable.

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, workflows and stat-cards, with history as a separate read. The combined /api/v2/platform-status/snapshot read is deprecated and returns Deprecation and Sunset headers, 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.

Was this page helpful?