> For the complete documentation index, see [llms.txt](https://docs.clusters.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clusters.xyz/introduction/concepts/cluster-name.md).
# Cluster Name
A cluster is a bundle of addresses where each address has its own unique name. For example, my cluster might be *foobar/* and I'd have three wallets each named *foobar/cold*, *foobar/memecoins*, and *foobar/gaming*, respectively. The part before the / slash is called the **cluster name**, the part after the / slash is called the **wallet name**.
A cluster name can be owned by a single individual - called a **personal cluster** name. Or a cluster name can be owned by a community such as an a blockchain, an NFT community, or gaming ecosystem - called a **community cluster** name.
Personal Cluster Examples:
* foobar**/**
* rye**/**
* vitalik**/**
Community Cluster Examples:
* treasure/
* pudgy/
* layerzero/
Personal clusters and community clusters act the same aesthetically and display across integrations. They're both bundles of addresses with wallet names. The difference is that community clusters have more advanced management tooling to manage thousands of community wallet names at the same time.
#### Requirements
* **Uniqueness:** Unlike .eth and .sol fragmentation, names are globally unique across all chain ecosystems. If you try to register a name that already exists, it will fail.
* **Length:** Names are stored as a bytes32 string. So the max length is 32 characters. As we role out unicode support such as emoji's, the max length will vary
* **Allowed Characters:** Supported characters include `a-z`, `0-9`, underscores (`_`), and dashes (`-`)
* **Case Sensitivity:** Cluster names are case insensitive. So `Foobar/` and `foobar/` will be treated the same.
---
# 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://docs.clusters.xyz/introduction/concepts/cluster-name.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.