Time-lock module for minimum holding-period enforcement

Configure the DALP time-lock compliance module so an asset enforces a minimum holding period before received units can be transferred.

The time-lock compliance module enforces a minimum holding period between receipt and onward transfer of an asset's units. DALP records the receipt block for each holder position and rejects outbound transfers whose source amount has not yet satisfied the configured lock period.

Use the time-lock for regulatory holding-period rules (Reg D 6-month holding, Rule 144 restrictions), employee-equity vesting where transfers are blocked until the vest date, or any operating model that requires a cooling-off period before secondary movement.

For the architecture reference, see Time lock.

Prerequisites

The asset already exists (configure during creation) or you have the Asset administrator role on the deployed asset.
The lock period (duration and any identity-based exemptions) is signed off by your operating team.

Configure during asset creation

In the Asset Designer compliance step, pick the time-lock module. Enter:

The lock duration (typically expressed in seconds or in human-readable units the wizard converts).
Any identity-based exemptions (operator wallets, treasury wallets, or specific OnchainIDs allowed to transfer despite the lock).

Configure on an existing asset

From the asset detail workspace, open the compliance tab and update the time-lock configuration. Changes apply forward; existing positions keep the lock period they were issued under.

Operating considerations

The lock applies to each receive event independently. A holder receiving units across multiple transactions can transfer the first batch as soon as that batch's lock expires, regardless of whether the later batches are still locked.
The module records receive timestamps as blocks. Transfers are evaluated against the configured period at the time of attempt; clock-skew is not an issue because the on-chain timestamp is authoritative.
Exemptions are identity-based. An OnchainID listed as exempt can transfer received units immediately. Removing an exemption applies forward; positions received under the exempt period stay unlocked.
Mint operations are always allowed by the time-lock module (the receiver acquires the lock starting at mint).

What stays external

The choice of lock duration, the legal basis (Reg D, Rule 144, vesting agreement), and the audit trail justifying exemption grants stay with your operating team.

Troubleshooting

What you see	What to check
Transfer rejected for an otherwise-allowed holder	Confirm the source units have satisfied the lock period since they were received.
Some units transfer, others rejected	The lock is per receive batch. Earlier batches may have unlocked while later batches remain locked.
Exemption granted but transfer still rejected	Confirm the exemption applies to the source OnchainID, not the wallet. The on-chain transaction granting the exemption must have confirmed.

Time lock