Skip to content
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

Closed
ryanxcharles opened this issue Feb 16, 2014 · 1 comment
Closed

Support merge avoidance #69

ryanxcharles opened this issue Feb 16, 2014 · 1 comment

Comments

@ryanxcharles
Copy link
Contributor

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

@maraoz maraoz added this to the v0.9 milestone Dec 19, 2014
@maraoz maraoz modified the milestones: v0.11, v0.9 Jan 21, 2015
@braydonf braydonf removed this from the v0.12 milestone May 11, 2015
@braydonf
Copy link
Contributor

braydonf commented Jun 6, 2016

Interesting, this likely applies more to these or similar repos now:

@braydonf braydonf closed this as completed Jun 6, 2016
micahriggan pushed a commit to micahriggan/bitcore that referenced this issue Dec 27, 2018
matiu pushed a commit to matiu/bitcore that referenced this issue Jan 14, 2019
matiu pushed a commit to matiu/bitcore that referenced this issue Jan 14, 2019
matiu pushed a commit to matiu/bitcore that referenced this issue Jan 21, 2019
matiu pushed a commit to matiu/bitcore that referenced this issue Jan 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants