# Overview

## Overview

Clusters is a universal namespace. All the blockchains, all your wallets, one name. 

Clusters is different than existing services. It's **one universal name** that encompasses all the blockchains. It's different than ENS' .eth, SNS' .sol, Avvy's .avax, SpaceID's .bnb and .matic, or UnstoppableDomains using arbitrary conflicting TLDs. It embraces the multichain world.

A clusters name is suffixed with a trailing slash: **/** 

So if I'm foobar, my clusters name is **foobar/**

All my wallets are then suffixed individually under this universal name, just like a website URL. My ethereum wallet could be **foobar/eth**, my solana wallet is **foobar/sol**, my bitcoin wallet is **foobar/ordinals**. I can also have multiple wallets on the same chain, for example **foobar/defi** and **foobar/nfts** can both be ethereum wallets. 

<figure><img src="https://1252323684-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOlyBmjWRNMw3jAapqxrM%2Fuploads%2FdQNZgMvhOoLbhheHFdo8%2FScreenshot%202024-02-19%20at%2010.04.04%E2%80%AFAM.png?alt=media&#x26;token=6d07aae5-5ace-4f8e-967c-2c52982947e6" alt=""><figcaption><p>A sample cluster containing two wallets: an EVM wallet and a solana wallet</p></figcaption></figure>

Clusters helps users create a **universal profile**.&#x20;

* Say a project wants to airdrop a Solana coin to all Pudgy Penguins holders. Before Clusters, there's no easy way to do this, you'd have to go manually collect addresses yourself and likely only get a fraction of the data you need. With Clusters, you can easily query which SOL addresses are linked to Pudgy Penguin EVM addresses.
* Say a user is trying to bridge Ethereum to Solana. They have to manually go open up their SOL wallet every time, copy paste the SOL address, and hope they didn't misclick on a block explorer spoofed transaction. Wasted time and energy. With Clusters, the bridge app can autopopulate which SOL address is in the same cluster as the EVM address they're bridging from. Smoother UX, fewer scams, and higher conversion rates for the app.
* Say a hot new blockchain app pops up, like Farcaster. Instead of yet another first-come first-serve squatter race where the app owner has to manually claw back names and face social backlash, cluster names can be easily integrated as first-class prioritization without pandering to one ecosystem over another.


---

# 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/overview.md?ask=<question>
```

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.