Skip to content

fix(L2-config): disable mempool sync on OP Stack and Arbitrum chains#1599

Merged
pragmaxim merged 2 commits into
masterfrom
fix/L2-config-cleanup
Jul 3, 2026
Merged

fix(L2-config): disable mempool sync on OP Stack and Arbitrum chains#1599
pragmaxim merged 2 commits into
masterfrom
fix/L2-config-cleanup

Conversation

@pragmaxim

Copy link
Copy Markdown
Contributor

On restart, L2 chains (OP Stack / Arbitrum) log:

initializeMempool EthSubscribe newPendingTransactions: invalid subscription type for subscribe

op-geth and arbitrum-nitro do not implement the newPendingTransactions subscription filter. Without disableMempoolSync: true, Blockbook logs this error on startup and repeatedly attempts to resubscribe.

This was already fixed for bsc_archive, polygon_archive, and base_archive but was missing on the remaining L2 coin configs.

Add "disableMempoolSync": true to:

Config Chain Node
optimism.json Optimism (full) op-geth
optimism_archive.json Optimism (archive) op-geth
base.json Base (full) op-geth
arbitrum.json Arbitrum One (full) nitro
arbitrum_archive.json Arbitrum One (archive) nitro
arbitrum_nova.json Arbitrum Nova (full) nitro
arbitrum_nova_archive.json Arbitrum Nova (archive) nitro

op-geth and arbitrum-nitro do not implement the newPendingTransactions
subscription filter. Without disableMempoolSync: true, Blockbook logs:

  initializeMempool EthSubscribe newPendingTransactions:
    invalid subscription type for subscribe

and wastes resources on repeated resubscribe attempts.

This was already fixed for bsc_archive, polygon_archive, and
base_archive. Apply the same fix to the remaining L2 coin configs:

  - optimism, optimism_archive
  - base
  - arbitrum, arbitrum_archive
  - arbitrum_nova, arbitrum_nova_archive
@pragmaxim
pragmaxim requested review from Copilot and cranycrane and removed request for Copilot July 2, 2026 18:00
…ncurrency

Trezor Suite's Blockbook websocket client caps concurrent in-flight requests
at 42 (blockchain-link/src/workers/blockbook/index.ts:481). The old default of
0 disabled the server-side limit entirely, making per-connection getAccountInfo
abuse bounded only by the 2500 msgs/10 min rate limiter.

Change the default to 42 so the server-side descriptor-count limit activates
automatically. The env var override is preserved for operators who want a
different value.
@pragmaxim
pragmaxim merged commit 3af322e into master Jul 3, 2026
4 checks passed
@pragmaxim
pragmaxim deleted the fix/L2-config-cleanup branch July 3, 2026 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants