258: txn-mempool-conflict

[xloem]

It seems if you foolishly use a private key from your wallet, you can double-spend coins before all the bsvup transactions have broadcast. This unfortunately leaves a bunch of unbroadcasted transactions that fail due to mempool conflicts. I guess they need to be regenerated with new coins.

Broadcasted 7f5704bee147fafd90b5167e22097583f8798b8ce6de0686fbca679864250353
Broadcasted f38435d9ffc5d4791685000fd319c944402a93e5b136b59c683154795d437ee6
236bc091c07132d6cde6a97e0b2b288c9c3e4a1e2e92fc8906a83f463e322a8f 广播失败，原因 fail to broadcast:
the transaction was rejected by network rules.
258: txn-mempool-conflict
Broadcasted 7b88bd9563b4a3067aea0a23553631cf70856b79c8f4c47d91cdcb8b666e913e
Broadcasted 26ba6756d532fd82830c7d4fc7f9b7997c0e1f6ba655dd720018f0a1aea3262b

[monkeylord]

Double spend is possible. However, it's spent from user, too. Therefor, I think it's safe, and can be avoided.

Using a wallet private key is not recommended, not only because it's possible to have double spend, but also because its TXs will flood the wallet.