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.
Currently, the xcall contract doesn't have read method for what the next
reqIdis, 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.