> For the complete documentation index, see [llms.txt](https://ben-on-xlayer.gitbook.io/benokx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ben-on-xlayer.gitbook.io/benokx/readme.md). # Welcome Every cycle, a new face shows up in crypto. Some come and go, some fade into the noise, but a few stick not because of tech jargon or corporate promises, but because they *actually are real*.\ \ Crypto is supposed to be fun, cool, chaotic and ours. \ However, these traits has died down over the years following baseless pump and dumps.\ \ But that’s exactly why **BEN** was created. He isn’t trying to be the next “serious” project with a 50-page manual. He’s here to bring the vibes back the laughter, the memes, the energy that first pulled us all into this space. BEN is that frog you can actually relate to, He’s not a promise of overnight riches he’s a symbol of survival, of not folding when things get tough, of remembering that crypto is as much culture as it is code. With BEN, you’re not just buying a token you’re buying into a movement that’s fun, unapologetic, and built for the community. --- # 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://ben-on-xlayer.gitbook.io/benokx/readme.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.