> For the complete documentation index, see [llms.txt](https://docs.dtravel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dtravel.com/papers/dtravel-dao-governance/how-community-members-can-vote/dtravel-snapshot.md). # Dtravel Snapshot The Dtravel Snapshot is dedicated to proposals involving Dtravel. In order to participate in Dtravel related proposals, you must hold a balance of 500 TRVL and be a current Dtravel community member. Soft proposals will be put forth for discussion and the Dtravel team will put together a formal proposal based on the discussion and feedback. Examples of Dtravel proposals: * Proposal Process and proposal templates * How the Dtravel DAO will be governed (e.g. through a Council) * Council composition and selection (dependent on the above) * Tokenomics parameters * Growth campaigns These are some examples but as the community provides feedback on what type of proposals they’d like to see, more will be added. The initial proposals will be focused on formalizing a lot of the governance framework and processes to set up the Dtravel DAO. --- # 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.dtravel.com/papers/dtravel-dao-governance/how-community-members-can-vote/dtravel-snapshot.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.