Update web-client transaction-getter to handle known transactions like the PoW client did #2218
+135
−55
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The PoW client by @mar-v-in did some genius handling of known transactions, which can be optionally passed to the client's
getTransactionsByAddress
method.It, and now this client too, make sure all known transactions are included in the receipts, unconfirmed known transactions are queried again (and confirmed if they are, returned as expired if they have expired), pending or unsent transactions are re-broadcast, known transactions not in the receipts are also rechecked.
Pull request checklist
clippy
andrustfmt
warnings.