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.

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

Does the message value need to be known before the verification? #1

Open
Andlyn666 opened this issue May 24, 2024 · 2 comments
Open

Comments

@Andlyn666
Copy link

Hi, I noticed that the value hex"01" is hard-coded in the verifySourceChainMessage function. Does this mean that the message value needs to be listened for through an event first, and then verified on the other chain?

@adaki2004
Copy link
Owner

It is just an example, hard-coded value, for being 0x1. Can be anything! We are just proving it - whatever it is.

@Andlyn666
Copy link
Author

It is just an example, hard-coded value, for being 0x1. Can be anything! We are just proving it - whatever it is.

Thanks for the reply. So, the message value should be obtained through other methods, like listening to an event from the source chain, right? Otherwise, we cannot verify it

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

No branches or pull requests

2 participants