This PR removes the Broadcasted event from the transactionWatch and the broadcasted field from the Dropped event.
The Broadcasted event was introduced to inform users about the transaction process.
However, the number of peers it contains does not offer any strong guarantees about the uniqueness of those peers; or if the transaction could be later included in the chain by those peers.
Further, the Broadcasted event is hard to enforce by load balancers; in cases where the server goes down without sending a Broadcasted event first.
This PR removes the
Broadcastedevent from thetransactionWatchand thebroadcastedfield from theDroppedevent.The
Broadcastedevent was introduced to inform users about the transaction process. However, the number of peers it contains does not offer any strong guarantees about the uniqueness of those peers; or if the transaction could be later included in the chain by those peers. Further, theBroadcastedevent is hard to enforce by load balancers; in cases where the server goes down without sending aBroadcastedevent first.I would love to get your thoughts on this
Closes https://github.com/paritytech/json-rpc-interface-spec/issues/132.
cc @paritytech/subxt-team