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
Currently, the xcall contract doesn't have read method for what the next reqId is, and if executeCall has been called for any arbitrary reqId. Though we can explore the tracker for this info, it'll be quite cumbersome, and it might make more sense to add methods in contract for these 2 things.
same for requests as well.
The text was updated successfully, but these errors were encountered:
Yes I think this feature would be necessary for the frontend to track status of the xcall (assuming the realtime event listener will not always be listening for respective events on the destination chain)
From the support side, we can only check this in the xcall-tracker. But, for application developers, it seems this will be necessary unless the api for xcall-tracker will be open. Nonetheless, we should add this in the next update of xcall.
Currently, the xcall contract doesn't have read method for what the next
reqId
is, and if executeCall has been called for any arbitraryreqId
. Though we can explore the tracker for this info, it'll be quite cumbersome, and it might make more sense to add methods in contract for these 2 things.same for requests as well.
The text was updated successfully, but these errors were encountered: