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

feat: add methods to get the current reqId, and get data saved on proxyReqs for that reqId #747

Open
izyak opened this issue Sep 22, 2023 · 3 comments
Labels
iBriz iBriz Team

Comments

@izyak
Copy link
Collaborator

izyak commented Sep 22, 2023

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.

@pragyanshrestha-ibriz pragyanshrestha-ibriz added the iBriz iBriz Team label Oct 2, 2023
@pragyanshrestha-ibriz
Copy link
Collaborator

Might be resolved by xcall tracker. Icebox for now.

@sharma66mahesh
Copy link

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)

@izyak
Copy link
Collaborator Author

izyak commented Jan 5, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
iBriz iBriz Team
Projects
None yet
Development

No branches or pull requests

3 participants