# Vision {% hint style="success" %} The Rise Savages DAO vision is to be the conduit for connection, collaboration, and prosperity among a burgeoning community of Play2Earn gamers. {% endhint %} Rise Savages empowers blockchain metaverse gamers to explore opportunities and co-create projects that build towards the long-term flourishing of the novel DeFi tokenized economies. Our thriving Rise Savages community members will work towards collaboratively increasing yield generation, and thus overall individual profits and rewards. Thus, Rise Savages gamers receive substantial economic benefits that would otherwise not have been easily accessible or cost-effective. Rise Savages DAO has a wide variety of goals and benchmarks for enacting progress in the metaverse. At the core, this involves enabling the individual goals of gamers through $RISE token and asset ownership as well as giving them participatory power to shape the future of the DAO itself. As well as a strategic goal to empower metaverse-native gamers to build the training structure that onboards new players from all walks of life to the world of decentralized, blockchain-based gaming. As technology allows more people to move more of their lives online, an entire digital economy is developing inside these new virtual worlds. *Rise Savages* builds real-world value from fundamental metaverse economics. **Big picture view**: Rise Savages is a self-organizing community aimed at constructing a more generative metaverse in service of a better world. --- # Agent Instructions: 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: ``` GET https://ethan-nelson.gitbook.io/rise-savage-whitepaper/vision.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.