> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/higher-learning/bsv-academy/bitcoin-whitepaper-series/section-10-privacy-bitcoin-whitepaper/linking-ownership-of-coins.md). # Linking Ownership of Coins The risk is that if the owner of a key is revealed, linking could reveal other transactions that belonged to the same owner. \- Satoshi Nakamoto, Bitcoin Whitepaper The risk of exposing a user's financial activities increases when the owner of a key is revealed. If a **user spends coins received from third parties** or **spends coins back to themselves as change**, it becomes possible to trace the ownership chain through the public ledger. This exposure can lead to unwanted scrutiny from malicious parties who understand how to analyze transaction data. To counteract this risk, users should **consider employing separate transactions for each input**. By spending inputs in completely separate transactions, users can avoid the possibility of linking their identity to a group of coins, thereby **enhancing their overall privacy**. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/bitcoin-whitepaper-series/section-10-privacy-bitcoin-whitepaper/linking-ownership-of-coins.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.