Closed lexnv closed 8 months ago
This PR ensures that the server accepts at least 4 transactionWatch subscriptions, similar to the transactionBroadcast API.
transactionWatch
transactionBroadcast
While at it, have defined the error codes returned by this API
-38000
-32602
Have also added a mention wrt invalid decoded transaction bytes in the Invalid event.
Invalid
cc @paritytech/subxt-team @tomaka
This can't be guaranteed, because transactions stay in the pool when a JSON-RPC client disconnects.
This PR ensures that the server accepts at least 4
transactionWatch
subscriptions, similar to thetransactionBroadcast
API.While at it, have defined the error codes returned by this API
-38000
- more than 4transactionWatch
subscriptions are created (identical error code with chainHead_follow)-32602
- Invalid Parameter from the rpc specHave also added a mention wrt invalid decoded transaction bytes in the
Invalid
event.cc @paritytech/subxt-team @tomaka