> 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/hierarchical-deterministic-keychains.md). # Hierarchical Deterministic Keychains **Hierarchical Deterministic Keychains** (HD wallets) represent a significant advancement in the management of Bitcoin keys. These wallets allow users to generate a virtually unlimited number of key pairs from a single seed. This capability not only **simplifies the process of managing multiple keys** but also enhances privacy by enabling users to create a new key for each transaction. In the event that a wallet is lost or destroyed, **users can recover their funds by re-creating the original seed**. This feature is particularly beneficial for **maintaining privacy**, as it allows users to avoid the risks associated with key re-use. By employing HD wallets, users can ensure that their transaction history remains private and secure, as each transaction can be linked to a unique key. --- # 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/hierarchical-deterministic-keychains.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.