`LackOfFundForMaxFee` flashblock processing error

[haardikk21]

2025-11-12T14:08:23.273202Z ERROR error receiving message error=WebSocket protocol error: Connection reset without closing handshake

The websocket connection occasionally being dropped here causing missing flashblocks and hence going out of sync temporarily is probably causing it then. We are aware and trying to fix the websocket stream. You can track the status of that here - https://status.base.org/ - unfortunately not much to be done about that on this codebase

There are also many of these unrelated WS error:

2025-11-12T13:33:20.177353Z ERROR could not process Flashblock error=failed to execute transaction: Transaction(Base(LackOfFundForMaxFee { fee: 5916527071810380, balance: 5780008259113915 })) tx_hash: 0x9dd8a6d97577145f7660f6404b81647dd19b03ebab736ca3c1d82680dc9dfdcf sender: 0xe8cc4da88830ba7db1e46944cb75e745fb02e204
2025-11-12T13:33:20.253223Z ERROR Received non-sequential Flashblock for current block, zeroing Flashblocks until we receive a base Flashblock curr_block=38082527 new_block=38082527

The problem is that it can take couple of minutes just to recover from any these errors.

Originally posted by @ron-elmekiesse-bloxroute in #178

To use a tracker for this issue

[haardikk21]

This is a known issue but the root cause is unclear. Happens rarely and unable to locally reproduce so far. Continuing to investigate.