# How does the Whitelisting process work

Getting whitelisted means your address will be eligible to participate in an IDO.\
Addresses are chosen at random, so if your address has more than 1 ticket in the submission, your chances of being chosen are higher. \
\
It’s important to note that you are not spending your TKO when you apply for an IDO:  your TKO holding just translates to the number of tickets submitted to the IDO in your name. The more TKO you hold in your wallet, the higher the chance of successfully whitelisted with our weight system.

**TKO Tiers for Whitelist:**

* 100+ TKO = Every ticket is worth 1 TPower (ticket)
* 400+ TKO = Every ticket is worth 1.1 TPower (ticket)
* 1,200+ TKO = Every ticket is worth 1.15 TPower (ticket)
* 4,000+ TKO = Every ticket is worth 1.20 TPower (ticket)
* 12,000+ TKO = Every ticket is worth 1.25 TPower (ticket)

\
Here are **some ways** to become eligible for whitelisting:

1. **Apply to a form** on the project that you wish to invest in.
2. **Lock TKO** on our [dashboard](https://tlaunchpad.io/dashboard) for 7 days, instead of keeping them in your wallet.&#x20;
3. **Complete your KYC** once you get the link in your email.
4. Frequently check **Your Applicant** statu&#x73;**,** you will be informed once your address is whitelisted.<br>


---

# 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://tlaunchpad.gitbook.io/faqs/ido/how-does-the-whitelisting-process-work.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.
