camosoul
Well-known member
Ah, there you go, limiting the scope to avoid the issue...Because neither the devs nor the wallet are stupid. PrivateSend balances and transparent balances are strictly and explicitly kept apart, that's why you have two balances shown after mixing. They never touch (which means it's also not gay).
The only way to force transparent dust and PS funds to touch is to privatesend coins to yourself, turning said coins transparent again, and then mix with the dust. That has no impact on privacy, because there is no privacy left to impact.
I never said PrivateSend Change. I said Dead Change.
Dust still exists. Change still exists. Every incoming TX that doesn't denominate evenly.
Since the only way you can combone your dust is to do a non-PrivateSend TX, the Dead Change issue still exists. You put your finger in the Change from PrivateSend hole of the Dead Change problem, but you didn't plug up the problem I was talking about, as @TroyDASH points out here. Dead Change can come from other places, and it's not fixed.
This would clearly apply to any and all dust smaller than a denomination no matter how it is achieved....if you do a regular tx and combine the create denominations dust with one of the final anonymized denominations, then you would be associating that non-private dust with the final denomination transaction, which I would imagine might severely weaken your privacy for other PrivateSend txs that you might have sent using vins from the same final denominate-tx (wouldn't it be like doing only one round of mixing?). I'd defer to @UdjinM6 to weigh in on this scenario.
And after thinking about it for a bit, I actually came up with a solution for it. Perhaps you can build upon this, or tell me why I'm stupid, but the basic premise seems like it would work...
I'd been toying the idea of a delayed PS mixing function that allowed a mix of 3 + N. Then I started thinking about the brilliant simplicity that got @UdjinM6 hired...
Since the "pile the change into a bigger VIN" problem can't be fixed by breaking it down, by definition, maybe it can be fixed by building it up?
What if a daily, weekly or monthly (or, in real terms, every 100 blocks, every 400 blocks, oer every 100 blocks, or better dynamically based on TX volume) "garbage collection" transaction was signed and created similar to the voting superblock?
Since the damning associations aren't made until the non-PrivateSend TX occurs, maybe EVERYONE could get together in one bigass TX? Sure, you just gave away associations...Or did you? Everyone was in it! Which one was whose? You'd need MN blinding or maybe a more robust onion routing for messaging... Essentially, you'd be making the same association as the original TX. You'd be giving away no more information than the original TX. To a 3rd party observer, it's nothing more than "Yup, that thing that happened certainly did happen."
That same mechanic could even facilitate the roll-forward notion for a rolling BlockChain instead of a perpetual one... Sort of. If built at protocol-level...
Normal PS mixing is all about speed. So, going the minimum 3, and going as fast as possible matters. This is why other possible modes of operation for PS are unacceptable. But, as Garbage Collection, other modes could work...
Feel free to tell me that there's no point to this, but I can clearly see a point to this.
At it's lowest form, "the dust problem" is still a thing and DASH isn't alone in having it. The only way to denominate a large collection of dust is to roll it into a bigger VIN. Even if it didn't do anything else, it still proves that all of those came from the same client. Maybe that's not catastrophic. Maybe that's not even bad. But it's still ungood. And it does seem fixable.
Perhaps I've generated my own distraction by calling it Dead Change. To me, that's exactly what it is...
Last edited: