A few more remarks with regards to PrivateSend mixing :
I'm not sure if its due to the different versions on Testnet or if its a complication from using PrivateSend multi-session, but so far most of my wallets are showing "pending" amounts in the overview section after having mixed to 100%.
These "pending" amounts wont clear, because certain PrivateSend Denominate transactions are not getting confirmed. So besides a few conflicted transactions, there are also unconfirmed transactions that are causing problems.
The pending amount on my TestDash 2 wallet self-cleared somehow, but some of my other wallets (i have 6 in total) did not self-clear and have the pending amount still visible in the overview.
Using "recover transactions 1" (zapwallettxes=1) gets these unconfirmed transactions re-added with a new date to mempool, but they are not getting confirmed and seem to actually mismatch with the number of transactions currently in mempool
(for example i have 7 unconfirmed transactions, but mempool only shows 4 current transactions). Same problem with using "recover transactions 2" (zapwallettxes=2), they get re-added to mempool but not confirmed.
Update 1 : after 30 minutes some of my unconfirmed transactions that i re-added through "recover transactions 2" are now getting confirmed and the "pending" amount disappears in overview.
I wonder if we could implement some kind of one-time check after a wallet hits 100% completion, to re-add any unconfirmed transaction to mempool automatically ?
Update 2 : example of a (for now) still unconfirmed transaction that was re-added to mempool 1 hour ago
Transaction ID: 0a3617791873f64febcd81bc437c44ed2933166d3f9905d4f37641f52c842805
Other observations :
Keys get renewed during mixing when below 100 + automatic backup : working
Mixing finishes and stops at 100% : working
Mixing rounds can be set higher then 8 : working
Multi-session mixing per block : working (although the advanced privatesend interface does get a bit crowded on overview with this option activated, because it shows the privatesend status messages of 4 mixing sessions. Personally i dont consider this a problem, they can always disable advanced privatesend interface)
Mixing transactions confirm : partially working (got a few conflicted transactions and also some unconfirmed transactions during multi-session mixing)
Memory Pool Usage : differs in kb per wallet (some match, some dont)
When wallets get stuck in sync, it normally helps to close and restart them.
I'm not sure if its due to the different versions on Testnet or if its a complication from using PrivateSend multi-session, but so far most of my wallets are showing "pending" amounts in the overview section after having mixed to 100%.
These "pending" amounts wont clear, because certain PrivateSend Denominate transactions are not getting confirmed. So besides a few conflicted transactions, there are also unconfirmed transactions that are causing problems.

The pending amount on my TestDash 2 wallet self-cleared somehow, but some of my other wallets (i have 6 in total) did not self-clear and have the pending amount still visible in the overview.
Using "recover transactions 1" (zapwallettxes=1) gets these unconfirmed transactions re-added with a new date to mempool, but they are not getting confirmed and seem to actually mismatch with the number of transactions currently in mempool
(for example i have 7 unconfirmed transactions, but mempool only shows 4 current transactions). Same problem with using "recover transactions 2" (zapwallettxes=2), they get re-added to mempool but not confirmed.
Update 1 : after 30 minutes some of my unconfirmed transactions that i re-added through "recover transactions 2" are now getting confirmed and the "pending" amount disappears in overview.
I wonder if we could implement some kind of one-time check after a wallet hits 100% completion, to re-add any unconfirmed transaction to mempool automatically ?
Update 2 : example of a (for now) still unconfirmed transaction that was re-added to mempool 1 hour ago
Transaction ID: 0a3617791873f64febcd81bc437c44ed2933166d3f9905d4f37641f52c842805
Other observations :
Keys get renewed during mixing when below 100 + automatic backup : working
Mixing finishes and stops at 100% : working
Mixing rounds can be set higher then 8 : working
Multi-session mixing per block : working (although the advanced privatesend interface does get a bit crowded on overview with this option activated, because it shows the privatesend status messages of 4 mixing sessions. Personally i dont consider this a problem, they can always disable advanced privatesend interface)
Mixing transactions confirm : partially working (got a few conflicted transactions and also some unconfirmed transactions during multi-session mixing)
Memory Pool Usage : differs in kb per wallet (some match, some dont)
When wallets get stuck in sync, it normally helps to close and restart them.
Last edited: