# Wallet 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**. #### Requirements * **Uniqueness:** There cannot be 2 wallet names that are the same under a namespace. So you cannot have an EVM address called `foobar/defi` and a solana address that is also called `foobar/defi` * **Length:** There are currently no limit to how long a wallet name should be. But it's encouraged to keep it under 10 characters. * **Allowed Characters:** Supported characters include `a-z`, `0-9`, underscores (`_`), and dashes (`-`) * **Case Sensitivity:** Cluster names are case insensitive. So `foobar/defi` and `foobar/Defi` will be treated the same. **Data structure -** A wallet consists of: * **Cluster Name:** What cluster name that wallet is attaached to * **Wallet name:** The shorthand name you give your wallet address * **Address:** The full length address of the wallet. It's then converted and stored in bytes32 format. * **Verification:** Verified wallets are unique to the entire ecosystem. You can't have a wallet verified on 2 clusters at a time. This represents priority when querying names. * For example: If 0x123 is on foobar/cold and 0x123 is also on rye/hot but verified, rye/hot will have priority when resolving a cluster via an address. --- # Agent Instructions: 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: ``` GET https://docs.clusters.xyz/introduction/concepts/wallet-name.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.