Don't clean mempool on catch-up

CounterpartyXCP · Jan 13, 2025 · cc12a62 · cc12a62
1 parent 562a8f0
commit cc12a62
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/counterparty-core/counterpartycore/lib/blocks.py b/counterparty-core/counterpartycore/lib/blocks.py
@@ -24,7 +24,6 @@
     gas,
     ledger,
     log,
-    mempool,
     message_type,
     util,
 )
@@ -1503,7 +1502,6 @@ def catch_up(db, check_asset_conservation=True):
                 fetcher = start_rsfetcher()
             else:
                 assert parsed_block_index == block_height
-            mempool.clean_mempool(db)
 
             parsed_blocks += 1
             formatted_duration = util.format_duration(time.time() - start_time)

diff --git a/counterparty-core/counterpartycore/lib/follow.py b/counterparty-core/counterpartycore/lib/follow.py
@@ -138,7 +138,8 @@ def receive_rawblock(self, body):
                 blocks.catch_up(self.db, check_asset_conservation=False)
             else:
                 blocks.parse_new_block(self.db, decoded_block)
-            mempool.clean_mempool(self.db)
+            if not config.NO_MEMPOOL:
+                mempool.clean_mempool(self.db)
             if not config.NO_TELEMETRY:
                 TelemetryOneShot().submit()
 

diff --git a/release-notes/release-notes-v10.9.0.md b/release-notes/release-notes-v10.9.0.md
@@ -42,6 +42,7 @@ The following transaction construction parameters have been deprecated (but rema
 - Have the node terminate when the `follow` loop raises an error
 - Don't stop the server on "No such mempool or blockchain" error
 - Handle correctly RPC call errors from the API
+- Don't clean mempool on catchup
 
 
 ## Codebase