-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Support merge avoidance #69
Labels
Comments
Interesting, this likely applies more to these or similar repos now: |
micahriggan
pushed a commit
to micahriggan/bitcore
that referenced
this issue
Dec 27, 2018
Chore/update deps
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Although bitcoin is naturally pseudonymous, it is very easy to leak personal financial information. A strategy to increase privacy is to never merge two outputs together. Instead, when sending a payment, send to many different addresses instead. This is called "merge avoidance". To my knowledge, this concept was first introduced by Justus Ranvier:
http://bitcoinism.blogspot.com/2013/07/reclaiming-financial-privacy-with-hd.html
And named by Mike Hearn:
https://medium.com/p/7f95a386692f
The text was updated successfully, but these errors were encountered: