> For the complete documentation index, see [llms.txt](https://docs.dappradardao.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dappradardao.com/dappradar-dao-report-2021-2023/financial-reporting-overview.md). # Financial reporting overview Since the TGE mentioned in the previous section, this section presents the financial disclosure from DappRadar DAO, spanning from December 14, 2021, to December 31, 2023. The financial information is organized annually—2021, 2022, and 2023—and primarily examines asset balances as they stood at the close of 2023. The financial information presented is derived from on-chain transactions, reflecting cash flows rather than adopting the accrual accounting principles. Given the nascent state of accounting standards for DAOs, DappRadar DAO is in the process of developing appropriate accounting methodologies and policies that best meet the informational needs of our stakeholders. Until a comprehensive accounting framework is established, we are presenting financial data akin to cash flow statements based on on-chain transactions. --- # 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.dappradardao.com/dappradar-dao-report-2021-2023/financial-reporting-overview.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.