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
We currently have a way to submit a transaction which also creates a subscription to the transaction status. However, most users of the node will still need to fetch the receipts after receiving the final status update. This requires the use of sticky sessions to ensure that the 2nd request for receipts goes to the same node that provided the status update.
Instead, we should include receipts on the final status update in the subscription. This simplifies the logic in the sdk to avoid making multiple requests, and also guarantees consistency without needing to use sticky sessions.
The text was updated successfully, but these errors were encountered:
Related issues:
- Closes#1364
This PR adds receipts to the transaction status objects returned by
transaction-related GraphQL queries. When querying for the status of a
transaction, a status of `Failed` or `Success` will now include the
transaction receipts.
Note that this PR does not remove Receipts from `OpaqueTransaction` or
other places that would constitute a breaking change, thus preserving
existing behaviour. We can remove receipts from redundant areas in a
follow up PR after the beta release.
We currently have a way to submit a transaction which also creates a subscription to the transaction status. However, most users of the node will still need to fetch the receipts after receiving the final status update. This requires the use of sticky sessions to ensure that the 2nd request for receipts goes to the same node that provided the status update.
Instead, we should include receipts on the final status update in the subscription. This simplifies the logic in the sdk to avoid making multiple requests, and also guarantees consistency without needing to use sticky sessions.
The text was updated successfully, but these errors were encountered: