Skip to content
This repository was archived by the owner on Mar 14, 2025. It is now read-only.

Don't require finality when fetching CCIPSendRequested in the execution phase#347

Merged
mateusz-sekara merged 4 commits intoccip-developfrom
exec-finality
Dec 4, 2023
Merged

Don't require finality when fetching CCIPSendRequested in the execution phase#347
mateusz-sekara merged 4 commits intoccip-developfrom
exec-finality

Conversation

@mateusz-sekara
Copy link
Contributor

@mateusz-sekara mateusz-sekara commented Dec 4, 2023

Motivation

We don't need to verify finality when executing messages. We rely on the fact that CommitReport was properly transmitted on-chain, and during the execution phase, nodes don't have to double-check that.
This is a tiny performance boost because nodes will reach consensus faster. This also reduces the number of error logs when nodes see different chain finality and can't fetch the logs used to build the Commit Report.

Commit Plugin remains unchanged and still heavily rely only on finalized logs

@mateusz-sekara mateusz-sekara requested a review from a team as a code owner December 4, 2023 06:52
@mateusz-sekara mateusz-sekara changed the title Don't require finality when fetching CCIPSendMessages in the Exec plugin Don't require finality when fetching CCIPSendMessages in the execution phase Dec 4, 2023
@mateusz-sekara mateusz-sekara changed the title Don't require finality when fetching CCIPSendMessages in the execution phase Don't require finality when fetching CCIPSendRequested in the execution phase Dec 4, 2023
@mateusz-sekara mateusz-sekara merged commit ac2921a into ccip-develop Dec 4, 2023
@mateusz-sekara mateusz-sekara deleted the exec-finality branch December 4, 2023 15:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants