Skip to content

fix: trace tracking should stop when reaching CCIPReceive #644

Draft
vicentevieytes wants to merge 1 commit intomainfrom
vv/trace-tracker-stop-condition
Draft

fix: trace tracking should stop when reaching CCIPReceive #644
vicentevieytes wants to merge 1 commit intomainfrom
vv/trace-tracker-stop-condition

Conversation

@vicentevieytes
Copy link
Collaborator

No description provided.

@vicentevieytes vicentevieytes changed the title trim trace tracker tree when reaching a CCIPReceive message fix: trace tracking should stop when CCIPReceive Mar 6, 2026
@vicentevieytes vicentevieytes changed the title fix: trace tracking should stop when CCIPReceive fix: trace tracking should stop when reaching CCIPReceive Mar 6, 2026
return true, (fmt.Errorf("failed to extract opcode from message in the trace: %w", err))
}
//Stop tracing on CCIPReceive message delivery
if uint64(opcode) == offramp.OpcodeCCIPReceive {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we make this part of SubmitTransaction or determine somehow based on the input? Placing this straight into the txm makes this generic component CCIP 1.6 specific and will break on future versions/other products

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would also require us to verify the contract address or we're vulnerable to spoofing if someone else deliberately uses this opcode downstream in the receiver

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants