Maturity redemption
How operators configure the maturity-redemption token feature during asset creation and trigger holder redemption when a fixed-income asset reaches its maturity date.
The maturity-redemption token feature handles the end-of-life redemption flow for fixed-income instruments. After the maturity date, an authorised operator triggers the redemption state, the feature transfers face value from the configured treasury to each holder, and the position burns. Holders cannot transfer after the maturity-state transition.
For the architecture reference, see Maturity redemption.
When it attaches
Bond, CD, and structured-note templates attach maturity-redemption. See the fixed-income, cash, and structured sections of the system templates catalog.
What you configure
In the Asset Designer details step, fill the maturity-redemption parameter block:
| Parameter | Description |
|---|---|
maturityDate | Date the instrument matures. Immutable after deployment for most templates. |
denominationAsset | ERC-20 token face value pays in. Typically the same token the instrument was priced in. |
treasury | Wallet that holds the denomination asset and funds redemption payments. |
faceValue | Redemption amount per token, in the denomination asset's units. |
The denomination-asset prerequisite is checked during template selection: if no compatible ERC-20 exists in the tenant, the template card is disabled until the operator creates or registers one.
What you operate
After deployment:
- Fund the redemption treasury before maturity. The treasury must hold at least
faceValue × totalSupplyof the denomination asset for redemption to settle every holder. - Trigger maturity on or after the maturity date through the asset detail workspace's maturity tab. The trigger moves the asset into redemption state; transfers and mints are blocked afterwards.
- Holders claim through the platform's redemption flow. The feature transfers face value from the treasury to the holder and burns the position.
- Reconcile leftovers: any treasury balance after every holder has redeemed stays in the treasury for the operator to reclaim.
Operating considerations
- The redemption-state transition is one-way. The platform does not support un-matureing an asset.
- The feature does not enforce the treasury funding step; if the treasury is short, holder redemption fails until the operator funds it.
- Pre-maturity transfers run through the asset's normal compliance modules. The maturity feature does not change transfer eligibility before the maturity date.
- Some templates fix the redemption treasury to the deploying wallet rather than asking for it during creation. Read the template detail in the catalog to confirm.
Troubleshooting
| What you see | What to check |
|---|---|
| Holder redemption fails after maturity | Confirm the redemption treasury holds enough of the denomination asset to cover face value for the requesting holder. |
| Maturity trigger rejected | Confirm the maturity date has passed and the trigger is submitted by an account with the maturity role. |
| Transfers still pass after maturity | Confirm the maturity trigger has confirmed on chain; the state transition is asynchronous. |
Read next
- Maturity redemption architecture
- Fixed treasury yield — often paired with maturity-redemption for coupon-paying bonds.
- System templates catalog
Permit
How the permit token feature enables EIP-2612 signature-based ERC-20 approvals on DALP assets, removing the need for a separate approval transaction.
Fixed treasury yield
How operators configure the fixed-treasury-yield token feature for periodic holder-claimed yield from a configured treasury wallet.