SettleMint
Changelog

Changelog

Find every user-visible capability, API change, and operator workflow update shipped in the 3.x line, with context for what to act on.

Patch releases are not published as separate posts. When a patch introduces something operators should know about, it is held for the next numbered changelog entry.

The newest line is a staging area rather than a record. It collects what has landed since the last release so the entries are written while the work is fresh, and it is marked as unreleased until that version is cut.

Releases

DALP 3.2: trading, income, and reporting

Not released yet. A permissioned order book for the assets you issued, instruments that pay income, regulatory filings with the record of who authorised each operation, with an SDK migration and new API rejection cases.

DALP 3.1: run the platform as your own

Bring your own custody per organization, deploy where no one else can reach, and run the platform with audited admin tools. No breaking changes.

DALP 3.0: design your own digital asset

Define a compliance policy once, apply it to every instrument, and let the chain enforce it on every transfer. Carries breaking changes; the release names the exact migration path.

xvp.settlement-expired.final

A settlement passed its cutoff without executing and a caller withdrew the escrow; each participant's escrow is returned through xvp.assets-refunded.final or parked through xvp.refund-deferred.final; sent once the chain finality watermark reaches its source block, and only to endpoints on the System that owns the settlement's factory.

DALP 3.2

Assets issued on the platform can now trade on its own permissioned order book, pay income to holders, and produce regulatory filings and audit records.

On this page

ReleasesDALP 3.2: trading, income, and reportingDALP 3.1: run the platform as your ownDALP 3.0: design your own digital asset