Random is the key word here I think. Client side randomness when choosing which outputs to use for the current Tx will greatly improve anonymity.Ah, I just read your post about convertibility (missed it somehow). However, I did implement a fix to the issue you describe in 11.0.10, as it was a known issue. The solution is that if you submit 1DRK x 10, you'll get back 1DRK x 10 back with no change. Beyond that, I've added a lot of random noise so each of those outputs will be used randomly (not all at once) to improve anonymity.
I will test this asap.
Thanks. denomination convertibility would be a huge benefit not only for the current implementation, but also for compatibility and scalability.Anyway, I like your idea. I might throw that together before InstantX while I'm in DS mode.
I am looking forward to this.
This is exactly what UdjinM6 suggested and I think its a good solution that would be even better if it would just be 100, 10, 1 without any additions due to easier compatibility between systems using different smallest denomination amounts (because they otherwise wouldn't be compatible).^
The denomination amounts are reserved though, which is why they have the extra satoshi added to them. What about this:
Each could be converted still, without having to use such common values.
I don't actually see a reason for DS denominations to be distinguishable from normal payment amounts except for the client to know which funds to use as inputs. This, however, can be separately kept track of by the client.
Last edited by a moderator: