> For the complete documentation index, see [llms.txt](https://btcjourney.gitbook.io/start/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://btcjourney.gitbook.io/start/so-why-do-we-need-banks/introduction.md). # Introduction Now that we have a better idea of the trust problems that exist with our current fiat money that we have stored in our bank accounts, and understand what the real world impacts are of breaches of this trust, we should discuss why we keep using banks and central banks in the first place. Essentially, this segment will attempt to answer how we got ourselves into this situation. We will start with a very short history of money and talk about why the hardest form of money won out. Specifically, the first segment will explain why the difficulty associated with producing more gold inevitably made it the best money for thousands of years. We will then talk about how gold got accumulated and centralized by banks and central banks over time, in an attempt to resolve some of the issues physical gold had as a form of money. In particular, how gold started to show its limits when the pace and scope of our commerce increased with improvements in communications technology. And lastly, we will talk about how this centralization inevitably led to the trust issues discussed before. --- # 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://btcjourney.gitbook.io/start/so-why-do-we-need-banks/introduction.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.