Intent Lifecycle
Every resource created through the Mure API is an intent and follows the same lifecycle.
Status States
| Status | Description |
|---|---|
draft | Intent created locally, not yet submitted to the chain. |
pending | Submitted on-chain; awaiting indexer confirmation. |
confirmed | Execution confirmed by the indexer across all involved chains. |
failed | Execution reverted or the deadline elapsed without settlement. |
expired | Intent reached its deadline before submission. |
finalized | Terminal. The finalization sweep closed a confirmed intent. |
State Flow
draft → pending → confirmed → finalized
↓ ↓
expired failed
Why one lifecycle?
Transfers, swaps, and bridges each used to need their own state machine: one for a local transfer, one for a DEX swap, one for a cross-chain bridge. A request that moves value to several places would have needed a fourth, because its items settle separately. Mure models every resource as an intent with one lifecycle. You learn the six states once, and monitoring, retry, and reconciliation work the same for every operation type.
A batch is one intent, not several: one order, one transaction, one status. The published type says batch when the intent carries more than one transfer, and each transfer keeps its own classification in metadata.transfers.