# Target

**Breach intersects with three multi-billion markets:**

**Social networks:** $39 billion\
**Gaming:** $184 billion and **2.89 billion gamers**\
**Cryptocurrencies:** $2 trillion&#x20;

Given the fact that **Breach is a semi-decentralized social platform for gamers,** our presence in the market is vital to our vision. Breach **tokenomics are based on our own token, $BRGG,** and it's going to be important for our projects' future and our audience who will use the token to benefit the most from platform.

Additionally, **Breach itself is a game.** People's profiles may become on-chain item they use on the social platform and playing native games with others to unlock on-chain items. As a result, **Breach intersects with all the above markets**.&#x20;

### Breach Audience

Our audience is comprised of **traditional and blockchain gamers**, social media users, and content creators that want their profiles to monetize content and grow their community.

They are the tech enthusiasts, the disruptors, the ones that live on the edge of the newest innovations. The ones that **embrace change and being different**.

They play traditional and crypto games for entertainment and education. They are passionate about their games and create content, stream and showcase their skills and share knowledge of their experience to help the gaming community.&#x20;

**Breach is a place for those who are seeking to live in the future.**


---

# 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://breach-gg.gitbook.io/breach-gg/market/target.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.
