refactor(core-transaction-pool): clear cached transaction ids after accepting block #2916
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.
Because of nonces, #2879 changed how the transaction pool processor removes cached transaction ids. They are now removed too early which effectively renders the cache useless. But with nonces it is not trivially possible to generate a different id anymore (without changing the payload) and thus if rejected once (e.g. sent too early or whatever) it will likely be rejected again for quite some time.
The only purpose of the id caching is to "debounce" the transaction broadcasts that happen between peers in the network. Without it, the processor would end up processing the same transactions multiple times, because the endpoint is hit multiple times with the same payload in a short timeframe.
This PR changes it so that the cache is cleared whenever a block is accepted instead. While that solution is still far from perfect, so is the transaction endpoint.
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
Does this PR release a new version?
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
develop
branch, not themaster
branchIf adding a new feature, the PR's description includes: