> 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/key-re-use-and-associated-risks.md).
# Key Re-Use and Associated Risks
As an additional firewall, a new key pair should be used for each transaction to keep them from being linked to a common owner.
\- Satoshi Nakamoto, Bitcoin Whitepaper
One of the critical aspects of maintaining privacy in Bitcoin transactions is the practice of **key re-use**. It is recommended that users generate a new key pair for each transaction **to prevent the linking of transactions to a common owner**. When a user receives funds into a re-used locking script, it becomes easier for observers to track the funds and their movement. This risk can be mitigated by adopting a strategy of **using a new private key for each incoming transaction**, effectively separating the digital coins on the ledger.
Most modern wallets are equipped with features that facilitate this practice through **Hierarchical Deterministic Keychains**. This technology allows users to **generate an effectively unlimited number of key pairs from a predetermined seed**, enhancing both security and 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/bitcoin-whitepaper-series/section-10-privacy-bitcoin-whitepaper/key-re-use-and-associated-risks.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
