Conversion minter API
How to grant mint authority and configure the conversion-minter feature on the target asset so it mints to holders when the paired source asset burns their position.
The conversion-minter token feature attaches to the target asset of a conversion pair. It mints to the target holder when the paired conversion feature on the source asset burns the holder's source position.
For the operator how-to, see Conversion minter how-to. For the architecture model, see Conversion architecture.
Configuration
No featureConfigs entry required. The feature is self-contained. The Asset Designer attaches it during target-asset creation when a paired conversion source asset is also being created or already exists.
Authorisation
The conversion-minter requires the source-asset conversion contract to hold mint authorization. The Asset Designer wires this during deployment when both assets sit under the same operating organisation. For cross-organisation conversions, the target asset's operator must explicitly grant the minter role to the source-side conversion contract:
POST /api/v2/token/{targetAddress}/roles/conversion-minter
{
"grantee": "0x..."
}grantee is the address of the source-side conversion contract.
Behaviour
The conversion-minter does not run standalone. It only mints in response to the paired conversion contract's burn-and-request flow. Routine conversions require no separate operator step.
Related
- conversion: required companion feature on the source asset.
- Feature constraints
conversion feature API reference
API reference for the conversion token feature: configuration, publishing and disabling priced triggers, setting the conversion window, the holder conversion request, and staged interest settlement.
DALP smart wallet API for integrations
Use the DALP smart wallet API to list account-abstraction wallets, inspect gas readiness, manage signers and modules, and coordinate multisig approvals.