Add an endpoint to return the status of the bridged message #1323
Assignees
Labels
graphql-api
Affects API of the GraphQL
Comments
|
I assume that this endpoint is meant to be on the client? And the bridge UI will have access to the client? |
|
We need to implement it in the |
MitchTurner
added a commit
that referenced
this issue
Sep 20, 2023
The bridge UI requires an client endpoint for querying the status of a specific `Message`, whether it has been spent or not. An additional variant is added for unknown messages, i.e. messages that can't be found in the DB. The lookup is by `Nonce`. I'm not sure if we would prefer some other discriminators, but that seems like the obvious choice when you're searching the entire space--IDK if it's the most efficient though. #1323 --------- Co-authored-by: Green Baneling <[email protected]>
|
Fixed with #1371 |
crypto523
added a commit
to crypto523/fuel-core
that referenced
this issue
Oct 7, 2024
The bridge UI requires an client endpoint for querying the status of a specific `Message`, whether it has been spent or not. An additional variant is added for unknown messages, i.e. messages that can't be found in the DB. The lookup is by `Nonce`. I'm not sure if we would prefer some other discriminators, but that seems like the obvious choice when you're searching the entire space--IDK if it's the most efficient though. FuelLabs/fuel-core#1323 --------- Co-authored-by: Green Baneling <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We use the
SpentMessagestable internally for the relayer and executor. But on the bridge UI we need to know the status of messages. There is a workaround based on the DA height, but it is safer to provide an endpoint to fetch this kind of information.The text was updated successfully, but these errors were encountered: