> 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/wiki/addresses-and-wallets/bitcoin-address/address-reuse.md).

# Address reuse

**Address reuse** refers to the use of the same address for multiple transactions. It is an unintended practice, reducing the privacy and security of the participants of the transactions. Most wallets use deterministic keychains and mask the generation of new addresses from the user making it easy and safe to maintain privacy.

1. Problems
2. Privacy Address re-use can impact user privacy, allowing anyone who sends or receives money to or from a particular address to see all of the transactions it is part of.
3. Security Security is also a concern as a thief only needs to gain access to a single key in order to compromise a wallet.
4. Attribution This content is based on content sourced from <https://en.bitcoin.it/wiki/Address\\_reuse> under [Creative Commons Attribution 3.0](https://creativecommons.org/licenses/by/3.0/). Although it may have been extensively revised and updated, we acknowledge the original authors.


---

# 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/wiki/addresses-and-wallets/bitcoin-address/address-reuse.md?ask=<question>&goal=<user_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.
