> For the complete documentation index, see [llms.txt](https://whitepaper.venus.vip/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.venus.vip/venusdao-introduction/venus-dao-origin.md). # Venus DAO Origin Venus is the goddess of love and beauty in Roman mythology; Venus is the brightest planet about 41 million kilometers from Earth; Venus is a symbol of love and freedom, light and hope. Venus DAO is a collaborative network of decentralized organizations formed by experienced foundations, developers, content creators, community consensus makers and blockchain enthusiasts in the blockchain industry. The members of Venus DAO have rich experience in the Internet and blockchain industry, and have made outstanding contributions to Bitcoin, Ethereum, Polkadot, Polygon and other public chains by participating in code contribution development, community consensus and ecological construction. --- # 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://whitepaper.venus.vip/venusdao-introduction/venus-dao-origin.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.