You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in #7918 and #2185, it might be of interest to disconnect from a peer when receiving transactions that could never have been valid.
Before implementing this behaviour we want to look into more details of such a behaviour. Namely:
The use case where a node sends transactions that could never have been valid;
Implications on the security and correctness model of Tendermint (how does the application know that it is this particular peer that should be removed, is this scenario not covered already by other layers in Tendermint, etc.);
What other changes in other parts of Tendermint should the implementation of this require;
If solution/problem still seem valuable, propose an implementation path taking into account potential need to refactor and change the p2p layer itself to support this.
The text was updated successfully, but these errors were encountered:
jmalicevic
changed the title
Research and document:- The use case for such behaviour;- Implications for the security and correctness model (how does the application know that it is this particular peer that should be removed, is this scenario not covered already by other layers in Tendermint, etc.);- What other changes in other parts of Tendermint should the implementation of this require;- If solution/problem still seem valuable, propose an implementation path taking into account potential need to refactor and change the p2p layer itself to support this.
mempool/p2p: Research the removal of bad peers based on CheckTx return code
Oct 13, 2022
jmalicevic
changed the title
mempool/p2p: Research the removal of bad peers based on CheckTx return code
mempool/p2p: Research implications of peer disconnect based on ResponseCheckTx
Oct 13, 2022
As mentioned in #7918 and #2185, it might be of interest to disconnect from a peer when receiving transactions that could never have been valid.
Before implementing this behaviour we want to look into more details of such a behaviour. Namely:
The text was updated successfully, but these errors were encountered: