> For the complete documentation index, see [llms.txt](https://palpaw-token.gitbook.io/palpaw/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://palpaw-token.gitbook.io/palpaw/about-us/who-we-are/team.md). # Team **Community Leaders** In stark contrast to the vast majority of memecoins in this space, the founding community leaders of PalPaw proudly disclose their involvement and are fully transparent. They have undergone doxxing, KYC procedures, and are recognized across the Web3 ecosystem for their professional contributions over the past several years. Within our community, everyone has the opportunity to assume a leadership role among their peers. We encourage all members to step up where they can, as we continue to evolve and expand each day. Those who commit to their peers and the community's growth will be acknowledged for their contributions in various ways. Below are some of the key leadership roles: * **Marketing:** Responsible for promoting PalPaw and engaging with the wider community to increase awareness and adoption. * **Development:** Dedicated to building and maintaining the technical infrastructure of PalPaw, ensuring its functionality and security. * **Design:** Focused on creating visually appealing and intuitive user interfaces, graphics, and branding elements for PalPaw. * **Moderators:** Tasked with maintaining order and fostering a positive atmosphere within the community platforms, addressing concerns, and enforcing community guidelines. * **Ambassadors:** Act as representatives of PalPaw in various online and offline spaces, spreading awareness and fostering partnerships. --- # 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://palpaw-token.gitbook.io/palpaw/about-us/who-we-are/team.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.