# Project Launch - How It Works

Each Blips campaign goes live on a **launchpad chosen by the project’s developers**.\
While the Blips process — interest registration, shuffle, deposits, and vesting — is always the same,\
the **final step (token launch and buy execution)** depends on the **launchpad** where the token is released.

At Tgmetrics, we adapt our process to fit each platform’s structure — always focusing on:

* **Fair access for holders**
* **Protection against snipers**
* **Best possible market entry**
* **Full transparency**

Below you’ll find how this works today for **Pump.fun**, with other launchpads (like Bonk, Believe, and Z Combinator) being added soon.

***

### Launch Workflow (All Launchpads except Z Combinator)

Every Blips launch, regardless of the platform, follows the same high-level logic:

1. **Project launches token** → Dev tokens are locked immediately.
2. **Early Access deposits are executed** → SOL from the Early Access pool is used to acquire tokens.
3. **Tokens are distributed** → Each participant receives a share based on their contribution.
4. **Vesting begins** → Unlocks happen progressively (35% at TGE + weekly).

The way these steps happen in practice depends on how the **launchpad** works.


---

# 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.tgmetrics.ai/blips/project-launch-how-it-works.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.