Authorized converters
Add or remove converter addresses for conversion-minter assets before running governed conversion workflows.
Authorized converters are conversion feature addresses that a conversion-minter asset accepts. Add a converter when a programme needs a governed route from a source asset into its target. Remove it when the operator retires, replaces, or withdraws approval for that route.
This guide covers the converter list only, for assets that already have conversion behaviour configured. Trigger setup and holder conversion are outside scope. For the wider conversion feature model, including triggers and conversion windows, read Conversion. For mandatory holder conversion, use Forced conversion.
Before you start
Confirm these points before changing the converter list:
- The target asset has the conversion-minter feature attached.
- The converter address belongs to a contract that exposes the conversion feature interface.
- The operator has the governance authority required to update the asset.
- The approval record names the asset, converter address, reason for the change, and expected route.
- Wallet verification is available for the submitting operator.
How the check works
The Console checks the converter address as you type it, before you reach wallet verification. Continue stays disabled while the Console checks the address or when the address has not yet passed. This gives you feedback before signing instead of after. The check confirms that the address is the conversion feature contract the asset uses for its route. A wallet address or any other contract fails authorization as a converter.
If the address fails the check as not a conversion feature contract, the Console shows a message asking for the loan token's conversion feature contract address and keeps Continue disabled. The on-chain enforcement is the final safeguard: if the check cannot complete because of a temporary issue, an add request submitted anyway is still rejected on-chain for an invalid converter.
API integrations should call the probe endpoint before sending an add request. A direct add request queues the update and relies on the contract to reject an invalid address.
Add an authorized converter
Open the conversion feature page
Open the asset detail page, then open the Conversion feature page. Confirm that the conversion-minter details are visible for the target asset.
Enter the converter address
Choose Add Converter. Enter the address of the loan token's conversion feature contract to allow for the asset.
Wait for the converter check
The Console checks the address as you type and keeps Continue disabled while it shows a rejected address. If the address fails, enter the conversion feature contract address for the intended route. A wallet address or unrelated contract fails authorization. If the check cannot complete because of a temporary issue, you can still continue; the contract enforces the requirement on-chain when you submit.
Submit with wallet verification
Review the confirmation screen, complete wallet verification, and submit the update. Keep the transaction result with the approval record for the converter change.
Remove an authorized converter
Remove a converter when the conversion route is no longer approved, the operator has replaced it, or the operating policy requires the asset to stop using that route.
Open the conversion feature page
Open the asset detail page and review the current authorized converter list on the Conversion feature page.
Start the remove workflow
Choose Remove Converter, then enter the converter address to remove. The platform confirms the address before you proceed to wallet verification.
Verify the operating impact
Before submission, confirm that no open conversion process depends on the converter address you are removing. Removing a converter stops future conversion requests that rely on that route; any in-flight process that already used the route is not affected.
Submit and record the result
Complete wallet verification and submit the update. Retain the transaction result with the reason for removal as part of the approval record.
API integration
Use the API path when an operator system manages converters instead of the Console:
GET /api/v2/tokens/{tokenAddress}/conversion-feature-probe?converterAddress={converterAddress}
POST /api/v2/tokens/{tokenAddress}/features/conversion-minter/authorized-converters
DELETE /api/v2/tokens/{tokenAddress}/features/conversion-minter/authorized-convertersUse the probe response before submitting an add request. Add and remove requests use the target token address in the path and the converter address in the request body.
Troubleshooting
| Issue | Check |
|---|---|
| Continue stays disabled | Confirm the address is the loan token's conversion feature contract, not a wallet, token, or unrelated contract. The Console keeps Continue disabled until you enter a valid conversion feature address. |
| Workflow is not visible | Confirm the asset has conversion-minter behaviour attached and that your operator has governance role. |
| Wallet verification fails | Complete the required verification method before retrying the update. |
| Conversion later fails | Confirm the relevant trigger, conversion window, holder balance, and converter list are still valid. |
Related guides
- Conversion for roles, triggers, conversion windows, and events
- Forced conversion for mandatory conversion workflows
- Token lifecycle API integration for conversion endpoints
- Per-asset RBAC for governance role context
How to force convert holder principal
Run a custodian-initiated conversion that bypasses the holder consent path, used for mandatory convertible instruments and institution-approved exception cases.
Manage on-chain token metadata
Add, update, or remove on-chain metadata entries on a deployed asset from the Console after issuance.