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, grpc only has a "SendAndSubscribe" endpoint for subscribing to transaction results. This has some benefits, particularly that you are guaranteed to be subscribing on the same node that originally send the tx, and so it knows about it before block is finalized.
It would be useful for users to be able to subscribe to tx results without sending, especially in the case where a connection was reset while waiting for the original result.
Add support for this to the websockets endpoint first. We can eventually add it to grpc as well.
The text was updated successfully, but these errors were encountered:
Currently, grpc only has a "SendAndSubscribe" endpoint for subscribing to transaction results. This has some benefits, particularly that you are guaranteed to be subscribing on the same node that originally send the tx, and so it knows about it before block is finalized.
It would be useful for users to be able to subscribe to tx results without sending, especially in the case where a connection was reset while waiting for the original result.
Add support for this to the websockets endpoint first. We can eventually add it to grpc as well.
The text was updated successfully, but these errors were encountered: