Open haerdib opened 3 years ago
Pushing this issue a little in importance, because Ajuna keeps having problem with the current setup, which gives multiple answers for one call (Submitted
+ InBlock
)
Maybe we could consider this issue in the next sprint?
That would be awesome, the more we can align with the usual RPC the more we can rely on libraries to make the client more resilient.
In the case of a TrustedCall, I suppose a good approach would be to get a an Id (or use the request id) and a call back of the client's method author_extrinsicUpdate (similar to substrate parity) with the updates (Submitted, InBlock, Finalized..).
In the case of a TrustedGetter, there is no need to send anything to watch, only one response I would assume.,
A client submitting a trusted operation (top) should be able to choose until which status event (
Submitted
,InBlock
,Finalized
..) the top is being watched.Additionally, only one answer should be returned, not multiple