Skip to content

Move CCIPMessageSent event to ccip-runtime#731

Draft
friedemannf wants to merge 1 commit into
ccip-interfacesfrom
ccip-events
Draft

Move CCIPMessageSent event to ccip-runtime#731
friedemannf wants to merge 1 commit into
ccip-interfacesfrom
ccip-events

Conversation

@friedemannf

Copy link
Copy Markdown
Member

No description provided.

@friedemannf friedemannf changed the title Move CCIPMessageSent event to ccip-api package Move CCIPMessageSent event to ccip-runtime Jun 26, 2026

choice FinalizeSend : FinalizeSendResult
with
eventEmitter : ContractId CCIP.API.EventEmitterV1.EventEmitter

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

i don't quite understand the event emitter idea. if we place the events in its own package, eg ccip-events - then it doesn't need to be upgraded even if ccip-core or ccip-runtime are upgraded, and the same event could be created across upgrade versions. even if we update events in the future, we can just create a second events package eg ccip-events-v2 but still emit both v1 and v2 events for backwards compat eg with observability. what does this abstraction give us?

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