moli
Well-known member
What do you mean "they should be combined manually first"? The total of those change amounts is less than 1.5 DRK, if they are sent back to the wallet, Darksend can't anonymize them, and they can't be spent in combo with the anonymized amounts.0.2125 is special change amount used for collaterals. As for everything else smaller than 1 DRK they should be combined manually first (at least for now).
Iirc, we didn't have this "stuck unconfirmed" amounts before the Core version, also the problem with the greyed DS transactions suddenly rolling back on the wallet Transaction screen (as shown in my previous post), so I did think probably it had something to do with the btc codebase, which I had seen on Testnet during v.11 testing also.That's a known issue. They do not "stuck" actually, those txes just have low priorities to be included in next blocks in terms of how bitcoin calculates it because of inputs low confirmations, small amounts of outputs and large size of the resulting txes - in terms of bitcoin that looks similar to "dust" or "bloating". There is a solution to this (not tested yet) but someone said "no more updates on mainnet pleeease!" :tongue: Seriously speaking, we need to get rid of most bitcoin segfaults/crashes to stabilize this version (which is mostly done), enforce payments and then continuedevelopmentdeployment. :wink:
If we're going to start testing InstantX tomorrow, I'm all for it. Thanks.