We’ve observed a behavioral difference between Ethereum and BSC when sending sequences of transactions with increasing nonce values.

In Ethereum:

It’s allowed to send transactions with a future nonce (greater than the current one).

These transactions enter the mempool and wait for the preceding (nonce - 1) transactions to be mined.

Once a previous transaction is confirmed, all subsequent ones are automatically picked up and mined without manual intervention.

Even after a temporary network outage, it’s usually enough to rebroadcast one or two payments for the chain to “unpack,” after which all subsequent transactions continue processing automatically.

In BSC:

Under the same conditions, after connection restoration, dozens or even hundreds of transactions remain in the submitted state and do not reappear in the mempool.

Each of these transactions must be manually rebroadcast to continue processing.

This behavior started around June 10, 2025 — before that date, the issue did not occur.