Movements
A movement is any action that moves value or changes an asset on-chain: a mint, a burn, a transfer, or an enforcement action such as a freeze, clawback or pause. Every movement starts from a vault, passes policy and compliance checks, and is signed by the vault's quorum.
#The New Movement wizard
Mints, burns and transfers are created with New Movement on the Movements page, in four steps:
- Movement type: Mint / Issue, Burn / Redeem, or Transfer.
- Source and destination: the vault, and for a transfer or mint, a whitelisted destination.
- Amount and asset: the asset, the amount and an optional description, then the policy checks.
- Review and submit: the summary, the checks and the signatures required, for example "2 of 3".
Enforcement actions are created from the asset page (see Enforcement) and appear in the same Movements queue.
#Policy checks
Step 3 runs every check before a transaction exists. A movement that fails any of them cannot be submitted.
| Check | Passes when |
|---|---|
| Whitelisted destination | The destination is on the asset's whitelist |
| Transaction limit | The movement fits the vault's and your role's remaining limit for the cycle |
| Sanctions screening | Your provider clears the destination (see Compliance) |
| Quorum approval | Shows the signatures the vault needs |
#Movement statuses
| Status | Meaning |
|---|---|
| Pending | Submitted, waiting for the first signature |
| Signing | Signatures are being collected toward the threshold |
| Broadcasting | The threshold is met and the transaction is being broadcast |
| Confirming | Broadcast, waiting for Bitcoin confirmation |
| Completed | Confirmed and applied |
| Failed | Could not be completed; review the details and resubmit |
Signing is the approval: there is no separate approve button. A movement that is not signed stays pending.
Read Mint / Issue, Burn / Redeem, Transfer, The signing workflow and Movement history.