> 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/public-records-and-transparency.md).
# Public Records and Transparency
The public can see that someone is sending an amount to someone else, but without information linking the transaction to anyone.
\- Satoshi Nakamoto, Bitcoin Whitepaper
The Bitcoin network operates on a principle of **public transparency.** However, the identities of the individuals involved in these transactions are not disclosed.
To further obscure transaction details, users can break payments into **multiple outputs or conduct several transactions**. This method not only enhances privacy but also allows users to maintain a secure online presence.
The Bitcoin ledger functions **similarly to stock exchanges**, which keep private records of trades while releasing only sanitized data regarding the price and size of transactions.
This dual-layer approach to record-keeping ensures that **while the public can see the flow of funds, the identities of the parties involved remain confidential.**
---
# 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/public-records-and-transparency.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.