Create transaction privacy page #175

[johnsBeharry]

type: page
title: Transaction privacy
permalink: /guide/payments/privacy
file: guide/payments/privacy.md

Problem

Just like the internet once something is public it's there forever. There is no silver bullet when it comes to preserving a user's privacy in bitcoin. It takes constant diligence, and not only can information leak from the user's own bad/uninformed choices, but a counterparty can cause the user's privacy to be compromised if there is a leak on their end.

Solution

• Don't reuse addresses
• Label coins with the names of the observer for easier coin selection
• Coinjoin
• Design with privacy in mind

Assumptions about the reader

1. Has read transaction structure

Result

• Click here to preview

---

Follow up tasks

• Create graphic showing points of compromise (wallet, node, post-confirmation/blockchain surveillance).
• Illustrate tracing ownership across a series of input destruction and creation events.
• Mention constraints like gap limit when generating a large amount of potentially unused addresses.

Closes#175

[danielnordh]

I've gone through the text specifically and committed wording and readability tweaks.
Good to go in my eyes. There's an outstanding comment from @GBKS about a link that should be addressed/closed.

[pavlenex]

Addressed the link thingy in d9b8210

We're good to go, great work everyone! 🚀