Subsequent transactions from an account fail to be included in blocks

[xendarboh]

The first txn (nonce 0) from an account succeeds as expected,
a second (nonce 1) fails (silently from caller/user perspective),
and third+ (nonce 1) is rejected as already exists in mempool.

Observed with multi faucet drips within the web app (or other modules).
Runtime module tests do not demonstrate the issue, sequencer does.

commit c698cad

$ pnpm env:inmemory dev --filter chain -- --logLevel DEBUG

...

│ Block collected, 0 txs, 0 messages
│ Produced block #0 (0 txs)
│ Block collected, 0 txs, 0 messages
│ Produced block #1 (0 txs)
│ Block collected, 1 txs, 0 messages
│ Produced block #2 (1 txs)
│ ---------------------------------------
│ Transaction #0
│ Sender: B62qpruoRCfGAcFWZhBSx3nr4Bu4ScrZnSP2Aiwtk5y1nLNQ9GhCPh4 Nonce: 0n
│ Method: Balances.addBalance
│ 
│ Arguments: {}
│ Status: true 
│ ---------------------------------------
│ Block collected, 0 txs, 0 messages
│ Produced block #3 (0 txs)
│ Assertion failed:  [Function (anonymous)]
│ Assertion failed:  [Function (anonymous)]
│ Block collected, 0 txs, 0 messages
│ Produced block #4 (0 txs)
│ Assertion failed:  [Function (anonymous)]
│ Assertion failed:  [Function (anonymous)]
│ Block collected, 0 txs, 0 messages
│ Produced block #5 (0 txs)
│ Transaction 24857548107922712534312845523269073286174772272724191478474205018996959620863 rejected: already exists in mempool
│ Assertion failed:  [Function (anonymous)]
│ Assertion failed:  [Function (anonymous)]
│ Block collected, 0 txs, 0 messages
│ Produced block #6 (0 txs)