Skip to main content

Burns and corporate actions on a restricted wallet

Which burns and corporate actions leave a restricted wallet out or burn its units in place, how a follow-up settles them, and why it cannot be force-converted.
Open it fromOrganisation participantsUsersWalletsRole:OwnerConsole address: /participants/users/userId/wallets

This reference explains how burns, corporate actions, forced conversions, and fund subscription settlements treat a wallet under a wallet restriction, why the platform refuses forced conversions of restricted holders, and how to settle skipped holders after lifting the restriction.

Burns and corporate actions

Operation
Treatment of a restricted wallet
Follow-up after lift
Burn (POST /api/v2/tokens/{assetId}/burns)
Skipped (returned in skipped), or returns 409 DALP-9590 if all skipped.
Re-submit burn for the wallet.
Buyback and Partial redemption
Skipped (state: "skipped", skipReason: "restricted"). Cash stays in treasury.
Select Continue this action (followsUpOn).
Reverse split, Capital decrease, Rights-issue close
Forced-burned in place (if eligible smart wallet), skipped, or ordinary-burned on legacy contracts.
Select Continue this action (followsUpOn) to settle skipped units or withheld cash.
Forced conversion
Refused (409 DALP-9590), nothing sent.
Re-submit Force convert while trigger and window remain open.
Minting corporate actions (bonus, forward split, token dividend)
Skipped if frozen on the minted token (skipReason: "restricted" or "frozen").
Select Continue this action (followsUpOn) (unavailable for spin-offs and tradable rights).

Before accepting a burn or confirming a corporate action, DALP checks active restrictions across the token's system on that network regardless of which tokens the restriction lists. Because checks run at confirm rather than preview, previews and approvals still list restricted holders (skipping cash-eligibility checks for them so unrelated cash-asset rules do not block the run).

Wallets restricted directly on the wallet restriction module (outside DALP or by another organisation on a shared system) are treated the same way while the module is enabled, except responses omit restrictionId and Console Lift restriction cannot lift them. Investigate who restricted the wallet via Cases from the wallet restriction module before lifting on chain, and run a burn preflight before retrying.

Burn

POST /api/v2/tokens/{assetId}/burns (and Burn tokens in the Console) omits restricted wallets and burns from remaining wallets, listing omitted wallets in skipped with base-unit amount. restrictionId is included only for Owners, Platform administrators, Compliance managers, and Custodians on a listed token, and module-only restrictions omit it. POST /api/v2/tokens/{assetId}/preflights with action: "burn" returns the same skipped list.

If every target wallet is restricted, DALP returns 409 TOKEN_ADDRESS_RESTRICTION_ACTIVE (DALP-9590) and sends nothing (single-wallet Booked movements burns always fail this way, and frozen v1 burn routes fail the entire batch if any wallet is restricted). Replaying a burn with the same Idempotency-Key returns the original result and skipped list. Adding newly unrestricted wallets requires a new Idempotency-Key.

Buyback and partial redemption

At confirm, DALP skips every restricted holder (state: "skipped", skipReason: "restricted"), leaving their units unburned and cash in the paying treasury. If no non-restricted holders remain, confirm fails with 409 DALP-9590. Fund redemption requests tied to a skipped buyback return to open.

Lifting the restriction does not settle skipped holders automatically. Open the completed action and select Continue this action (or pass followsUpOn in the API) to run a follow-up for skipped holders (Continuing a partial run).

Reverse split, capital decrease and rights-issue close

At confirm, DALP chooses one of three paths based on contract version and executing wallet:

Token contract
Executing wallet
Outcome for restricted holder
DALP 3.2 token contract
Smart wallet holding both Custodian and Supply management on the token
Burned in place via forced burn
DALP 3.2 token contract
Missing either role, or not a smart wallet
Skipped (same as buyback)
Older contract (such as an original asset family)
Any
Burned via ordinary burn (older contracts do not check address freezes on burn)

For a rights-issue close, the table evaluates the rights token. Tokens issued from templates upgrade to DALP 3.2 via System updates.

  • Burned in place: DALP batches ordinary and forced burns together. The wallet stays frozen and restricted while its units burn (applied with transaction hash, so match active restrictions at confirm to identify forced burns). In a reverse split paying cash for fractions, DALP withholds cash (cashOwed with reason: "restricted"). After lifting, run Continue this action (followsUpOn) to pay withheld cash once (tracked in cashOwed.paidBy).
  • Skipped (left out): No units burn and no cash pays (skipped, skipReason: "restricted"), common when segregation of duties separates Supply management and Custodian. Reverse splits and capital decreases return 409 DALP-9590 if no other holders remain, whereas rights-issue closes still complete for remaining holders, leaving lapsed rights unburned until a follow-up after lift.
  • Excess application refunds: Wallets frozen on the subscription asset have refunds withheld in rightsExcess (cashOwed, reason restricted or frozen) and paid in a follow-up after unfreezing.
  • Older contracts: Ordinary burn runs normally, while reverse-split fractional cash is still withheld as cashOwed until a post-lift follow-up.

Forced conversion

Force convert on the token's conversion page (POST /api/v2/tokens/{assetId}/features/conversion-minter/forced-conversions) converts a holder's units into the target token without the holder's signature. Because conversion pays the wallet in another token, DALP refuses forced conversions of a restricted holder and sends nothing.

When your organisation holds an active restriction on the holder in the token's system, or the holder is restricted on the enabled wallet restriction module, DALP returns 409 TOKEN_ADDRESS_RESTRICTION_ACTIVE (DALP-9590) before checking wallet verification, under every debt method. The refusal names the holder and includes restrictionId only for the callers listed under Burn.

Only the Platform API runs this check. The contract does not read wallet restrictions, and under the mark-as-converted debt method units remain in the wallet while the contract skips its freeze check, so a Custodian calling the conversion contract directly outside DALP is not blocked.

Because DALP reads the module from indexed chain state and checks once on acceptance, restrictions added after the last index sync or after request acceptance do not block an accepted conversion (which converts under mark-as-converted). Once the restriction is lifted, run Force convert again while the trigger is active and the conversion window remains open.

Mints to a restricted wallet

On minting corporate actions (bonus issue, forward split, token dividend), DALP skips holders frozen on the minted token (skipReason: "restricted" or "frozen"), failing confirm with 409 DALP-9590 if none remain. After lifting, run Continue this action (followsUpOn) to mint skipped units. Spin-offs and tradable rights issues mint onto a new token and cannot be followed up, so confirm fails if any holder is frozen there.

See Restricted holders and Frozen holders in a mint for API payloads.

Fund subscription settlement

When settling a fund's subscription day (batched up to ten investors per transaction), DALP checks active organisation restrictions and the wallet restriction module once before recording batches. Restricted investors' requests are rejected immediately (state: "rejected", rejectionReason: "restricted") with no cash pulled and no units minted, while other investors settle normally (if every investor is restricted, all requests reject without failing the call).

Replaying with the same Idempotency-Key re-checks restrictions for batches still outside the transaction queue, returning newly restricted investors' requests to open so the next settlement rejects or settles them based on live state. Restricted investors can still lodge requests and must submit new ones after lifting. Outside settlements, the receiving treasury can still spend existing stablecoin allowances unless the wallet is frozen on that stablecoin.

Was this page helpful?