1. Keep the four lifecycle phases distinct
The official CCIP 2.0 message lifecycle describes Send on the source chain, Verify by offchain attestations, Index to collect verifier data, and Execute on the destination chain. A status UI should tell users which phase it has actually observed; a source transaction and a destination execution result are different evidence.
Do not map an API status, executor view, verifier result, and onchain execution enum into one undocumented “pending” value. Keep each source and its timestamp visible to support teams.
2. Show the destination OffRamp state separately
| OffRamp state | Value | Application meaning |
|---|---|---|
UNTOUCHED | 0 | No destination execution has been recorded. The cause may be pending verifier data or execution setup; do not label it failed from this state alone. |
IN_PROGRESS | 1 | A destination execution attempt is running. |
SUCCESS | 2 | Execution completed. Treat this as final and do not offer replay. |
FAILURE | 3 | Destination execution reverted. Diagnose the recorded error and address the cause before retrying. |
`UNTOUCHED` can describe a message that has not run, a missing required verifier entry in the indexer, or an expired automatic-execution retry window. Check the required execution inputs before presenting manual execution as ready.
3. Diagnose a failure before offering a retry
A recorded `FAILURE` does not automatically mean the receiver contract is wrong. The documented causes include receiver logic or gas, token handling, missing verifier data, an invalid manual submission, or insufficient outer transaction gas. Show the recorded error and keep recovery instructions specific to the observed cause.
- Keep the source transaction hash and CCIP message ID together.
- Use API fields such as overall message status, executor status, and verifier details as diagnostics.
- Treat `readyForManualExecution` as a convenience signal; it may be false while a message is still recoverable.
- After each execution attempt, read `OffRamp.getExecutionState(messageId)` again.
- Retain `ExecutionStateChanged` history when a failure is later followed by a successful retry.
A successful outer transaction receipt alone may not tell the full story. Before displaying “delivered,” check the destination execution state and the recorded error or event history.
4. Application acceptance checklist
- Display source chain, destination chain, message ID, and source transaction reference.
- Label source confirmation, verification/indexer progress, and destination execution separately.
- Do not label `UNTOUCHED` as `FAILURE` without additional evidence.
- Do not expose replay after `SUCCESS`.
- For `FAILURE`, show the recorded error and require the underlying cause and execution inputs to be checked before retry.
- Write user-facing copy that distinguishes automatic execution from an application-side recovery action.
5. Explore the local state walkthrough
Open the interactive status walkthrough. It uses synthetic values to demonstrate separate lifecycle and OffRamp state panels. It does not connect to a wallet, RPC, CCIP API, or contract and does not send transactions.
Scope and attribution
This is an independent DappWeb engineering note based on public documentation. It is not authored, reviewed, or endorsed by Chainlink, and it does not report a live integration for Chainlink, OlympusDAO, or another customer. DappWeb can discuss a separately scoped wallet, contract/API, status-flow, testing, and source-handoff engagement.
For project scope, see the DappWeb Chainlink card and DApp development service.
Official references
Discussion context: Chainlink’s 6 November post on the OlympusDAO CCIP migration. The post is a topic reference only; this guide does not reproduce or claim that application’s integration.