> 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-inputs-in-transactions.md).
# Linking Inputs in Transactions
Some linking is still unavoidable with multi-input transactions, which necessarily reveal that their inputs were owned by the same owner.
\- Satoshi Nakamoto, Bitcoin Whitepaper
Despite the privacy measures in place, some linking is unavoidable in **multi-input transactions**. When a user creates a transaction that aggregates multiple inputs to produce a larger output, it becomes **possible to trace the coins back to a single owner**. While the public ledger does not explicitly identify the owner, knowledgeable observers can **infer ownership based on the inputs used** in the transaction.
To mitigate this risk, users can adopt strategies such as ensuring that they always spend a larger output than the payment itself. However, this is not always feasible, and there are instances where aggregating coins is necessary. Therefore, users must remain vigilant and employ best practices to protect their 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/linking-inputs-in-transactions.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.
