> For the complete documentation index, see [llms.txt](https://capy-frens.gitbook.io/capy-frens/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://capy-frens.gitbook.io/capy-frens/capy-frens-project-overview.md). # CAPY FRENS — Project Overview Welcome to **CAPY FRENS**, a project built around fun, community spirit, and the iconic chill energy of the capybara. In a fast-moving Web3 world, CAPY FRENS brings something different—**good vibes, wholesome culture, and a light-hearted ecosystem designed for both memecoin lovers and NFT collectors**. At the heart of the project is our main character: a cute, relaxed, and friendly capybara that represents unity, positivity, and togetherness. This character sets the tone for everything we build—whether it's tokens, NFTs, or future community-driven experiences. ### **What is CAPY FRENS?** **CAPY FRENS is a Web3 ecosystem built around the $CAPY token and the upcoming Capy Frens NFT collection.**\ Our mission is simple: * Spread joy and good vibes * Build a strong, community-first ecosystem * Deliver fun and sustainable utility * Bring the “capybara energy” to the blockchain The project blends meme culture, heartwarming visuals, and Web3 utility in a way that feels refreshing, organic, and built for long-term engagement. *** ### **$CAPY Token Launch** We begin our journey by launching the **$CAPY token on PumpFun** — the core asset that fuels the entire CAPY FRENS ecosystem. #### **Why PumpFun?** PumpFun is known for: * Fast and fair launches * Strong meme communities * Organic viral growth opportunities * A perfect environment for fun, community-driven tokens The $CAPY token will act as the **main gateway** to our upcoming utilities and serve as the foundation for everything that follows. Once $CAPY gains traction and establishes a healthy community, we will begin expanding the ecosystem with the Capy Frens NFT collection and additional features. *** ### **Capy Frens NFT Collection** After the token launch, we will introduce the **Capy Frens NFT collection**—a series of unique, lovable, and personality-driven capybara characters.\ Each NFT will represent: * A member of the CAPY FRENS world * A unique identity within the community * A potential gateway to future utilities, perks, and ecosystem features The collection will expand the project’s visual identity, deepen the lore, and create new ways for holders to engage with the brand. *** ### **Ecosystem Vision & Flywheel Model** CAPY FRENS is built with long-term sustainability in mind. We’re adopting a **Burn Loop** **inspired model**, ensuring that: * Community activity strengthens the ecosystem * Token demand naturally increases through utility * NFT and token interactions support each other * Growth creates more value for loyal holders #### **Flywheel Philosophy** The more the community engages, trades, and participates, the stronger the project becomes. Parts of the ecosystem will contribute back to: * Token strengthening * NFT ecosystem growth * Long-term treasury sustainability * Reward loops for the community Our goal is to build a **self-sustaining, feel-good ecosystem** where vibes, value, and community grow together. --- # 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://capy-frens.gitbook.io/capy-frens/capy-frens-project-overview.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.