Independent builder walkthrough · dappweb
Where is a CCIP message?
Step through offchain lifecycle milestones and destination execution separately. This illustrates how an application can keep “not executed yet” distinct from “execution reverted.”
1. Offchain and source-chain progress
The lifecycle phases are separate from the OffRamp execution enum below. Advancing this panel does not change destination-chain state.
- 1 · SendSource-chain message
- 2 · VerifyOffchain attestations
- 3 · IndexVerifier data collection
- 4 · ExecuteDestination-chain OffRamp
Current lifecycle view: Send · source-chain message observed in this simulation.
Required execution inputs: not confirmed in this simulation.
2. Destination execution state
- Message ID
- DEMO-CCIP-001
- CCIP API view
- not connected
- OffRamp readback
- UNTOUCHED
- Retry cause
- not applicable
3. Keep the signals distinct
- CCIP API message, executor, and verifier fields help diagnose progress.
readyForManualExecutionis a convenience signal, not the final onchain state or a complete readiness guarantee.- Read
OffRamp.getExecutionState(messageId)after an execution attempt. - Use
ExecutionStateChangedhistory to distinguish a failure followed by a later successful retry.
Do not show “delivered” from the outer transaction receipt alone. An execution attempt may still leave the OffRamp in FAILURE; inspect the message state and recorded error.
Simulation log
- Simulation reset: OffRamp state is UNTOUCHED; no network request was made.
Official references
Created by dappweb. “Chainlink” identifies the ecosystem discussed; it does not imply official partnership or endorsement.