Token controls

Pause, blocklist, freeze, force-transfer, and delegate roles

📨

Available on enquiry. General availability is planned for Q1 2027. To activate Tokenisation now, speak with [email protected].

Token controls let an issuer act on a token after deployment, for example to stop transfers during an incident or to meet a legal order. Each control is a transaction from the vault that holds the relevant role, approved by its signers.

ControlERC-20 Managed issuerERC-3643Liquid AMP2 Transfer-restricted
Pause and unpause all transfers✅✅—
Blocklist an address✅——
Allowlist holders—✅ (register identities)✅
Freeze an address—✅—
Freeze part of a balance—✅—
Forced transfer between holders✅✅—
Delegate roles to other vaults✅——

The ERC-20 Standard templates, and the Liquid AMP2 Standard and Issuer types, have no controls.

ERC-20 Managed issuer roles

RoleAllows
AdminGranting and revoking the other roles
MinterMinting
PauserPausing and unpausing
ComplianceBlocklisting, forced transfers, and burning from holders

The deploying vault holds all four roles. You can give the minter, pauser, and compliance roles to other vaults at deployment or later, for example so a separate operations vault can pause the token without being able to mint.

ERC-3643

The deploying vault is the token's owner and agent. Controls on ERC-3643 tokens also include updating a holder's identity or country, and adding or removing compliance modules. See ERC-3643 and ONCHAINID.


Did this page help you?