Token operations
The actions authorized issuers and agents use to manage a token's lifecycle.
Authority before action
The connected wallet must hold the contract role required for the operation. A workspace administrator may be allowed to prepare an action without having the wallet authority to execute it. A Safe-controlled action follows its proposal, co-signature, and execution process.
Operating controls
| Operation | Purpose |
|---|---|
| Mint | Create tokens for a recipient, subject to the operation's checks |
| Burn | Remove tokens through an authorized supply operation |
| Pause or unpause | Control whether ordinary transfers can proceed |
| Freeze a wallet or an amount | Restrict movement of holdings covered by that control |
| Forced transfer | Move tokens using an authorized agent operation |
| Recovery | Move holdings to an approved replacement wallet under the recovery process |
| Manage agents | Assign or remove the relevant contract's operational permissions |
| Configure compliance | Update supported rules such as supply, holding, and jurisdiction limits |
Privileged operations do not necessarily follow the same checks as ordinary investor transfers. A pause or freeze should not be presented as disabling every possible administrative operation.
Recovery is an authorized process
The token contracts support recovery involving a replacement wallet and identity checks. This is distinct from restoring a wallet's private key. In the T-REX implementation, recovery moves holdings through a forced transfer; it does not burn the old balance and mint an equivalent new one.
The ability to perform recovery belongs to authorized agents and depends on the contract's requirements. It should not be described as a user-controlled password reset.
Review, sign, confirm
Review the intended recipient, amount, rule change, or role assignment before signing. Preflight checks can expose a likely refusal, but another transaction or configuration change can alter the outcome before execution.
A submitted request, a collected Safe signature, and a confirmed transaction are different stages. Verify the final result before repeating an operation. If the transaction is confirmed but a portal still shows old data, account for indexing delay before assuming the operation failed.