Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Retrieve MessageHash in XcmScheduleTask test cases #85

Open
chrisli30 opened this issue Aug 11, 2023 · 1 comment
Open

Retrieve MessageHash in XcmScheduleTask test cases #85

chrisli30 opened this issue Aug 11, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@chrisli30
Copy link
Member

Similar to the task creation logic on Turing, that we retrieve a taskId at the end of a sendExtrinsic call, Xcm tasks should also return an Id, which is the message hash, for developers to be able to know what task is scheduled. Then, we use the message hash to find the taskId on Turing chain.
@chrisli30 chrisli30 added the enhancement New feature or request label Aug 11, 2023
@chrisli30
Copy link
Member Author

XCM message hash is an intermediate step. As long as we can listen to the TaskScheduled event, the message hash can be skipped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chrisli30 @imstar15