> For the complete documentation index, see [llms.txt](https://docs.collective.name/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.collective.name/core-concepts/community-governed-treasury.md). # Community-Governed Treasury The DAO treasury is a fully on-chain pool of digital assets visible to everyone, governed and controlled by the community only A treasury is the community's shared wallet, but In a DAO, the treasury is special: it has no private key that any single person keeps. It sits under the control of the DAO's own voting system and the only way funds move is through a proposal the members voted to pass. Nobody can quietly reach in and take from it, No single wallet, not the creator's, not the platform's can move funds unilaterally. ***How it fills:*** While a minimum of 50% of every trading fee flows in automatically from the trading fees, anyway still can send any asset to the treasury public address --- # 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.collective.name/core-concepts/community-governed-treasury.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.