You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
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?
The text was updated successfully, but these errors were encountered: