> For the complete documentation index, see [llms.txt](https://docs.bstable.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bstable.finance/the-bstable-dao.md). # The bStable DAO bStable’s stablecoin AMM and its ‘savings accounts’ along with its payment protocol are built to be decentralized, community-owned, non-custodial products which can be integrated into other decentralized finance products. As such, the goal of the bStable team is to ultimately hand over governance of the protocols to the community of BST holders, while continuing to update the user interface and develop new products on top of the core payment protocols. While the DAO won’t be live upon launch, it is scheduled to go live within 2021. Once it is live, the bStable DAO will make decisions regarding any potential changes to the protocol, including but not limited to changes to the fee structures, reserve allocation, and BST distribution. --- # 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.bstable.finance/the-bstable-dao.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.