-
Notifications
You must be signed in to change notification settings - Fork 740
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Snowbridge: Emit sent event from BH to AH #6965
base: master
Are you sure you want to change the base?
Conversation
05e56c4
to
4d754da
Compare
@@ -160,6 +160,8 @@ pub mod pallet { | |||
}, | |||
/// Set OperatingMode | |||
OperatingModeChanged { mode: BasicOperatingMode }, | |||
/// A XCM message was sent. | |||
Sent { destination: Location, message: Xcm<()>, message_id: XcmHash }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Including the full XCM message in the event makes it too big. You can add debug logging for full XCM, but for the event topic_id
and message_id
should be enough.
Sent { destination: Location, message: Xcm<()>, message_id: XcmHash }, | |
Sent { destination: Location, message_id: XcmHash, topic_id: XcmHash }, |
You can populate topic_id
for example like this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Btw: message_id
is generated from Ethereum and we sent it through all the way along. By using WithUniqueTopic the topic_id
is just same as message_id
(i.e. the t of the last instruction SetTopic(t)
)
c0a33e8
to
fab5bc9
Compare
Sent
event for the xcm to AH.MessageReceived
event ahead for less confusion.