v3.1.3.1 attempts double-spend?

[placer14]

While using client v3.1.3.1, I was making small spends to the same address. (400-500 uLTC each) I was purposefully trying to spend just above the dust limit to exercise the accounting and detection of these transactions on mainnet for our wallet which is under active development.

At one point, I received the following error and believe it might be the result of the client (erroneously) attempting a double-spend of some previously used utxo. Is this something I can help you troubleshoot?

error: {'message': 'the transaction was rejected by network rules.\n\n18: txn-mempool-conflict\n[01000000010405173c7917869f680dde0eee974f2f666d43174a011a013d1d57a2ddffc2b6010000006a473044022036a262688f564bc7f318258212e620e49052e4fb28f0327afbfd83166d64bf3b0220397836ba101382900306ca4f5e3036cb1eed696d1fda72c607aa0e6b53d41ea50121029095fed582e6235c9d4d172af2e4adc3d0b8a2af9b47f473df77e2184baeb3a5fdffffff0250c30000000000001976a9148e08f5c4836e385cf3ab8d7af76a9be50a3547fd88ac29bddb01000000001976a9148cc51fcad8876ec48541719812375d37e5a5e98788ac42bf1700]', 'code': -1}

[pooler]

It would be useful to have a sequence of steps to reliably reproduce the issue.

Also, you may want to try with version 3.3.2.1. There are currently no binaries for it, but you can get it from the git repo.

[placer14]

This is likely a transient issue related to the state of the mempool, so I doubt I can provide steps within a controlled environment which reliably produce the error. I can tell you that this wallet has:

• 18 receive addresses which each having at most 2 txs against it
• 3 send addresses, one with 52 txs against it, and the other two with 2 txs against it. The address with the large volume of txs currently holds the entirety of my wallet balance (which around 300 mLTC).

At the time of the error, I was sending output from within this wallet to my test wallet with no more than 3 transactions in the mempool (unconfirmed) at one time. When the error occurred, I had at least 1 (but no more than 2) unconfirmed txs in the mempool. The error persisted on each additional attempt regardless of what I did to change the amount (but never raised the fee above the lowest setting). It wasn't until my prior transaction had gotten a confirmation that I was able to spend funds again.

Hope this info is helpful.

[placer14]

(Note: there are additional receive/sending addresses which are unused, I was only enumerating the number of used addresses above.)