-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use input address instead of change address #1241
Comments
i like the idea. maybe using a mutliple choice checkbox (the kind where you can only pick one) to choose between 'do not reuse addresses' as default 'return change to the same address' as second choice and with coin control enabled 'use custom change addresses' as a third option. the return address should be based on the last utxo selected to keep it simple. |
not a bad idea for those not wanting privacy so much. Would need to decide which input change would go and yes would not be hard to do |
AFAIK this not only hurts your own privacy but then also the privacy of anyone you interact with. Once it's obvious which is the payment and which is the change, then profiling becomes much simpler for observers. |
I am going to close this. The existing functionality which allows customizing the change address to be the same as the sending address is good enough, and I am not sure whether providing a check box is the right move to change the default behavior without a treatise on the ramifications. |
For normal transactions, it should be possible to transfer the change back to the originating input address instead of generating new change addresses (at least opt-in, maybe opt-out). There is a chance of losing coins if one does not backup the wallet. As there is already the feature "use custom change address" in the GUI, I guess it is not hard to put in the input address.
The text was updated successfully, but these errors were encountered: