> For the complete documentation index, see [llms.txt](https://byat.gitbook.io/byats-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://byat.gitbook.io/byats-whitepaper/welcome.md). # Welcome! Official Supporter of Bonk's Great Asset **Why** Bonk, the reigning champion, emerged from humble beginnings, weathered Solana's 2023 capitulation, rose from the ashes, and now stands proudly with a billion-dollar market cap. The question isn't if, but when Bonk will seize the TOP 1 Meme coin throne. At Byat, we're dedicated to propelling its rightful ascent. **How** In the crypto community, we often witness tokens skyrocket just as we're left contemplating missed opportunities. At Byat, we're here to change that narrative. Our commitment involves holding a substantial portion of our value in Bonk, distributing them during major events. This strategy creates a time buffer, enabling latecomers to realize gains similar to early investors. Additionally, we meticulously align our DEX liquidity with Bonk's performance to bridge any gaps not covered by our Bonk holdings and distribution. **What** We're a persistently tenacious community. Never settling for less, staying hungry, and staying foolish. Consider us an extension of Bonk's robust community—more than just members, we're family. Our social media footprint will be just as crucial to Bonk's success as its own. Being the first of its kind, we hope to inspire many more projects to support Bonk as it reaches new heights. Being a member of Byat means you're ambitious. Let's make headlines and break all conventions. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://byat.gitbook.io/byats-whitepaper/welcome.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.