> For the complete documentation index, see [llms.txt](https://docs.flaunch.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flaunch.gg/updates/17-november-launch-of-groups.md).

# 17 November: Launch of Groups

## What’s New

* **Launch a Group**: Creators and communities can now launch their own *Groups*, forming coin economies around cultural memes, creator tokens, or even third-party assets.
* **Group Coin**: Each Group is centered around a **Group Coin**—a base token used to denominate and capture value from all trading and derivatives activity inside that Group.
* **Earn on Trading**: Group owners can enable a **10% creator revenue fee**—paid out automatically from trading activity within the Group.
* **Modular Permissions**: Set Group permissions to **open** (anyone can add coins) or **closed** (only the owner can), with full modularity for future permission models.
* **Group as Cultural Registry**: Groups serve as repositories of cultural and derivative assets tied to the Group Coin IP. Think memecoins, forks, extensions—fees from their trades go to the Group economy.
* **Withdrawals and Ownership**: Group owners can withdraw assets directly. Future support for **sub-Groups** allows fractional asset control without parent Group ownership transfer.

## Why it matters

* Groups shift coins from single tokens to structured economies. By aligning creator and community incentives around a Group Coin, cultural memes and onchain assets can compound value over time.
* Whether you’re launching your own token or building around another, Groups give you the rails to coordinate, monetize, and grow your coin’s ecosystem.

#### Links

* Launching a Group : <https://docs.flaunch.gg/for-creators/getting-started/launch-a-group>


---

# 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://docs.flaunch.gg/updates/17-november-launch-of-groups.md?ask=<question>&goal=<user_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.
