Failed to accept tx in mem pool?

[skironDotNet]

PIVX v5.3.2

[furszy]

Check the debug.log, the rejection reason will be stated there.

[skironDotNet]

Not much in debug.log

2021-10-28T17:11:02Z CommitTransaction: ERROR: Failed to accept tx in the memory pool (reason: (code 0))
Transaction canceled.

[furszy]

ok thanks, there are some mempool rejections that aren't logging the cause.

[skironDotNet]

But had some weird behavior in the wallet. I selected over 100 inputs but under 150.
So now tx history it's showing me that transaction as conflicted (despite Failed to accept tx), and one of my addresses got a new amount, like a change, but doesn't make sense. I think I need to rescan my wallet, but if this change input won't disappear, then it means I got some free pivx out of nowhere (joke: wish I could replicate million times and got more free pivx).

So there is some bug... I'll get back with more details once the TX is fully rejected, and I re-scan the wallet .
I checked that failed tx and not shown in the explorer so I guess the bug is I got some change... unless my wallet had some missing TXs and after this one it rescaned that change? because the date is from 6/13
This would kind of explain why failed to sign tx, due to some hanging invisible tx...

[skironDotNet]

There is no way to reproduce. I have some suspicions, that when you introduced a new verison from 5.0.0, to now maybe HDSeed is not honored in the wallet. I was using HDSeed to make sure I won't lose the wallet. but now took the backup from March and have some funds gone, meaning, some new addresses non HDSeedwere generated in the old wallet...

[skironDotNet]

Caused by having un-scanned spent input, see #2615 for actual bug