From 6fc0f1e0259d9f914d9646bcd6e437ca12f752cb Mon Sep 17 00:00:00 2001 From: Jasmina Malicevic Date: Tue, 8 Nov 2022 11:00:26 +0100 Subject: [PATCH] Minor edits --- docs/rfc/rfc-026-p2p-bad-peers-checktx.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/rfc/rfc-026-p2p-bad-peers-checktx.md b/docs/rfc/rfc-026-p2p-bad-peers-checktx.md index fd2151f41..deb85afc7 100644 --- a/docs/rfc/rfc-026-p2p-bad-peers-checktx.md +++ b/docs/rfc/rfc-026-p2p-bad-peers-checktx.md @@ -326,6 +326,7 @@ However, this approach has several downsides: us transactions the entire time between two blocks. - If we want to keep track of when peers sent us a traansaction and punish them only if the misbehaviour happens frequently enough, this approach makes it hard to keep track of when exactly was a transaction submitted. +- Rechecking if optional and node operators can disable it. On the plus side this would avoid adding new logic to the mempool caching mechanism and keeping additional information about transaction validity. But we would still have to keep the information on peers and the frequency at which they send us bad transactions.