> For the complete documentation index, see [llms.txt](https://docs.leadfi.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.leadfi.org/product/reserves-and-transparency.md). # Reserves & Transparency leadBTC is intended to be fully backed 1:1 by Bitcoin reserves. ### What we publish * **Canonical reserve addresses** for on-chain verification. * **Token contract addresses** on supported EVM networks. * **Explorer links** for both BTC and EVM transactions. > Always verify addresses inside the official app interface. Never trust addresses shared by third parties. ### How to verify (high level) 1. **BTC side**: View the reserve address on a public explorer (e.g., mempool.space) and check balances/transactions. 2. **EVM side**: View the leadBTC token contract on the chain’s block explorer and check total supply. 3. **Compare** outstanding leadBTC supply with reserves (adjusting for pending settlements). More detailed proofs (e.g., dashboards, audit summaries) will be announced in-app and on our official channels. --- # 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://docs.leadfi.org/product/reserves-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.