> For the complete documentation index, see [llms.txt](https://ethan-nelson.gitbook.io/rise-savage-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ethan-nelson.gitbook.io/rise-savage-whitepaper/our-story.md). # Our Story It all started with five friends. They were all being rewarded considerable crypto assets through the P2E games that they were playing but quickly became frustrated with the inability to pool together their earned tokens and contribute to the game in a more collaborative way. They were asking themselves “*Why isn’t there a way to pool together a collective treasury with all of their group earnings and leverage it to produce higher yields?”* Introducing *RISE SAVAGES DAO*, a solution to this problem and a subsequent community of gamers, for Web3 gamers, by Web3 gamers. Where everyone wins! ### Core Team The founders will be the core team and the earliest participants of the DAO. Growth will start with early investors, asset owners, and players in the blockchain gaming and NFT space. $RISE token holders will eventually replace the early team as administrators of the protocol. --- # 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://ethan-nelson.gitbook.io/rise-savage-whitepaper/our-story.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.