Rethinking nonce management

[3commascapital]

hi there, i am trying to figure out the reason for some of the logic in the sender.js file it seems, when there is a large queue of messages / retries to work through that it loops and chooses nonces to use erratically. here is an example of what i am seeing. I have removed other data from the log lines. is this caused by 2 queues operating concurrently perhaps?

Sending transaction with nonce 21782
Sending transaction with nonce 21775
Sending transaction with nonce 21775
Sending transaction with nonce 21783
Sending transaction with nonce 21775
Sending transaction with nonce 21775
Sending transaction with nonce 21784
Sending transaction with nonce 21775
Sending transaction with nonce 21775
Sending transaction with nonce 21785
Sending transaction with nonce 21775
Sending transaction with nonce 21775
Sending transaction with nonce 21775
Sending transaction with nonce 21786
Sending transaction with nonce 21787
Sending transaction with nonce 21775
Sending transaction with nonce 21775
Sending transaction with nonce 21788
Sending transaction with nonce 21775
Sending transaction with nonce 21775
Sending transaction with nonce 21789
Sending transaction with nonce 21775
Sending transaction with nonce 21775
Sending transaction with nonce 21775
Sending transaction with nonce 21790
Sending transaction with nonce 21775
Sending transaction with nonce 21775
Sending transaction with nonce 21775
Sending transaction with nonce 21791
Sending transaction with nonce 21775
Sending transaction with nonce 21791
Reading nonce
Forcing update of nonce