What the developer wrote
Authored by MarcoFalke
test: Remove unused CUSTOM_._COUNT
Unused after commit cf3ab8e1d0a2f2bdf72e61e2c2dcb35987e5b9bd
What changed, and why it matters
This commit simply removes two unused variables from a single test file. It does not change any production code, network behavior, or security logic. There is no security relevance.
No action needed; this is a routine cleanup commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit deletes the constants CUSTOM_ANCESTOR_COUNT and CUSTOM_DESCENDANT_COUNT from test/functional/mempool_updatefromblock.py, noting they became unused after a prior commit. This is a pure test-code cleanup with no functional or security impact.
Changed components
test/functional/mempool_updatefromblock.pyInspect captured patch +0 / −3
diff --git a/test/functional/mempool_updatefromblock.py b/test/functional/mempool_updatefromblock.py
index 11571f6f..a5b2b6ce 100755
--- a/test/functional/mempool_updatefromblock.py
+++ b/test/functional/mempool_updatefromblock.py
@@ -19,9 +19,6 @@ from test_framework.mempool_util import DEFAULT_CLUSTER_LIMIT
MAX_DISCONNECTED_TX_POOL_BYTES = 20_000_000
-CUSTOM_ANCESTOR_COUNT = 100
-CUSTOM_DESCENDANT_COUNT = CUSTOM_ANCESTOR_COUNT
-
class MempoolUpdateFromBlockTest(BitcoinTestFramework):
def set_test_params(self):
self.num_nodes = 1
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.