Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Refactoring transaction handling in network #5915

Closed
NikVolf opened this issue May 6, 2020 · 0 comments · Fixed by #5939
Closed

Refactoring transaction handling in network #5915

NikVolf opened this issue May 6, 2020 · 0 comments · Fixed by #5939
Assignees
Labels
J0-enhancement An additional feature request.

Comments

@NikVolf
Copy link
Contributor

NikVolf commented May 6, 2020

  1. Network TransactionPool trait should return future on import and shouldn't spawn it's own task.
  2. Reputation handling should be managed on the side calling the above future.
  3. We should charge reputation from any peer that forced us to validate transaction (and refund it once we know it is not invalid).
  4. We shouldn't propagate all new transactions to all peers (but to max(sort(NUMBER_OF_PEERS), 5))
@NikVolf NikVolf self-assigned this May 6, 2020
@bkchr bkchr added the J0-enhancement An additional feature request. label May 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
J0-enhancement An additional feature request.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants