# The Blue Badge
As Avalanche grows exponentially, we need a way to understand which tokens, contracts and addresses are relevant to the community and actually what they say they are.
There could be (and mostly are) many AVAX [tokens](/how-to-use-avascan/avalanche-tokens-list.md) on Avalanche, but only one is the genuine native token. In the same way, there are many duplicate tokens and it's hard for users to understand which one is the genuine, and how to avoid scams or contracts different from what they're expecting.
So, we're working with Ava Labs, as well as setting up our own team of forensic on-chain analysts, to get in contact with all the genuine projects on Avalanche, mapping their addresses, contracts and tokens, knowing the teams, to give them the **Blue Badge**.
The Blue Badge is **Avascan's way of telling users** that the Avascan staff is in **active contact** with the team developing the project, and that there's an ecosystem partnership between Avascan and the project's team. It's shown in the Avalanche Token List and in Search Results: tokens, addresses and contracts with the Blue Badge are **listed higher** in the list after a transition period of about two weeks, in which tokens are only sorted by market cap by default.
The Blue Badge is given to addresses, contracts and tokens of dapps that:
* Are **relevant** in the Avalanche ecosystem
* Are **known community projects** (e.g. meme coins)
* (Tokens) have **sufficient liquidity** on DEXs, such that it's easy to buy and sell a few thousand dollars worth without an excessive price movement (less than 2%)
Avascan will improve the requirements over time over feedback from the community.
In order to get the Blue Badge, the project's team needs to show **commitment** to Avascan and the Avalanche ecosystem with one of these activities:
* Sharing every address, token and contract address on-chain, as well as notify Avascan's staff of new ones deployed/created
* Working to compile and publish every contract's source code ([Verify Contract](https://avascan.info/blockchain/c/contract/verify))
* Set Avascan as the default explorer to show transactions and addresses on-chain or, if the project doesn't have a website or a way to show those data, linking the token contract on Avascan in the homepage or other relevant page.
To get started with the process, fill this form:
---
# 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.avascan.info/programs/the-blue-badge.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.