# Launcher

The Bio Protocol V2 launcher uses the Ignition Sale to introduce new projects to the ecosystem. This model is designed to be transparent, community-driven, and to bootstrap a healthy secondary market from day one.

## Launch Types

Bio Protocol supports two tracks for launching projects on the platform. Both tracks use the same launchpad mechanics. The difference lies in the level of Bio involvement and the degree of customization available.

*In short: Community Launches prioritize scalability and a lower barrier to entry. Curated Launches prioritize selectivity and deeper support. Both tracks share the same launchpad mechanics.*

### Community Launches (Permissionless)

Community Launches are the permissionless track. Any team that meets the launchpad's baseline criteria can launch through the platform with lighter Bio involvement and a simpler, lower-barrier setup.

These launches follow a standard permissionless template covering tokenomics, raise size, and milestones. This template may evolve across the first launches as it is refined, but is designed to become the default. Bio still provides the launchpad infrastructure, agent tooling, and ecosystem visibility, but its post-launch involvement, especially in market liquidity management, is limited. Projects can build a track record here and potentially graduate into deeper engagement over time.

### Curated Launches

Curated Launches are the higher-touch track. These are projects Bio actively selects and supports, with deeper diligence, more hands-on collaboration, and custom tokenomics, funding structure, and launch design.

This track is for launches where Bio intends to be directly involved in shaping and supporting the project, including post-launch.

## The Ignition Sale

Projects are launched through a sale in which the token price is set from the beginning and all participants receive the same price, allowing for a predictable and fair distribution.

**Key Mechanics:**

* **Denomination:** All sales are denominated in `USDC`.
* **Raise Goal:** A launch is only successful if the total amount of `USDC` committed by the community meets or exceeds the predefined raise goal. If the goal is not met, all committed funds and points are returned to the users.
* **Duration:** Sales run for a fixed period.

## How to Participate

To participate in a launch, users need to perform two actions:

1. **Commit USDC:** You must commit the amount of `USDC` you wish to invest in the project.
2. **Pledge BioXP (optional):** You can optionally pledge [BioXP](/bio/introduction/bio-protocol-v2/staking-and-vebio/bioxp.md) ("Bio Experiment Points") to increase your allocation priority if the sale is oversubscribed. No minimum BioXP required to participate. If you commit USDC without pledging any BioXP, you are treated as having pledged 1 BioXP, the lowest priority weight. If a sale concludes at or below the target, allocations are determined by USDC contributions alone. BioXP only affects allocation when a sale is oversubscribed.

Note: Once USDC is committed to an Ignition sale, it's locked until the sale ends. It can't be withdrawn while the sale is live. Refunds are only issued after the sale closes, and only to eligible participants.

**Important:** Users should participate in launches via the Bio front-end. Participations via Basescan or other on-chain function calls made outside of the front-end will not be included in finalization if those wallets do not have an account on the platform and XP spent on the launch. Funds committed from such transactions will be ignored and refunded after the launch.

Launch participants must interact with and participate in launches via the Bio front-end to be included.

## Oversubscription & Allocation

It is common for launches to be oversubscribed, meaning the community commits more `USDC` than the target raise amount. In this scenario, your final allocation is calculated pro-rata based on the BioXP points you pledged, up to a maximum cap.

The final allocation is determined by the following formula:

`user_allocation = min((user_points / total_points_pledged) * tokens_for_sale, 0.005 * tokens_for_sale)`

Where:

* `user_points` is the amount of BioXP you pledged.
* `total_points_pledged` is the total BioXP pledged by all participants.
* `tokens_for_sale` is the total number of tokens available in the launch.

**Important Considerations:**

* **Max Allocation:** To ensure broad participation, a single user cannot purchase more than **1%** of the total token supply during the Ignition Sale.
* **Refunds:** If you commit more `USDC` than your final allocation allows, the excess `USDC` will be returned to you.

## Launch Outcomes

The outcome of each token launch shall be determined based on the amount of USDC contributed by participants relative to the stated funding target:

* **Underfunded Launch (< 100% of target):** The launch is deemed unsuccessful. Users may manually claim their committed `USDC` and pledged BioXP via the Platform. No tokens are issued, and no liquidity pool is created.
* **Fully Funded Launch (= 100% of target):** The launch is deemed successful. All contributed `USDC` is automatically paired with $Token to form an initial liquidity pool on a supported AMM. Users may claim their $Token allocation via the Bio Platform.
* **Oversubscribed Launch (> 100% of target):** Token allocations are distributed pro rata based on the amount of BioXP pledged by each user relative to total BioXP pledged in the sale. Users who committed USDC without pledging BioXP are treated as having pledged 1 BioXP. Any excess `USDC` not applied toward the final allocation shall be manually claimable by the user via the Bio Platform.

## Vesting & Staking

* No vesting schedule for Ignition Sale participants. Tokens are fully liquid immediately upon claiming after sale finalization.

## Limit-Sell Fundraising

Projects unlock funding as they achieve market traction around valuation targets.

* A percentage of each project’s token supply is reserved to be sold gradually as the project’s market value grows.
* Sales are made via transparent DEX limit orders once the project’s valuation remains above certain FDV thresholds, continuing to sell incrementally as the token achieves higher valuation milestones.

## Assets Types

The Bio Launcher supports Ignition Sales for different asset types in the Bio ecosystem, including: [IP Tokens](/bio/introduction/concepts/ip-tokens.md), [BioAgents](/bio/introduction/bioagents.md) and [BioDAOs](/bio/introduction/biodaos.md)

IP Tokens are often generated and overseen by a BioAgent or BioDAO that can retain a % of the IP-Token supply, passing value back to the community.

***

## Related Information

**Earning BioXP:**

* [**Staking Overview**](/bio/introduction/bio-protocol-v2/staking-and-vebio.md) - Earn BioXP through staking
* [**Staking BIO**](/bio/introduction/bio-protocol-v2/staking-and-vebio/staking-bio.md) - Stake BIO for veBIO and BioXP
* [**Staking Ecosystem Tokens**](/bio/introduction/bio-protocol-v2/staking-and-vebio/staking-other-assets.md) - BioXP earning strategy

**Participating in Launches:**

* [**Join Launches**](/bio/descientists/launch-an-asset.md) - Complete guide to launch participation
* [**Fund Guide**](/bio/descientists/quickstart-guides/fund.md) - Step-by-step funding walkthrough
* [**Launchpad FAQ**](/bio/introduction/bio-protocol-v2/launchpad-faq.md) - Common questions about the launcher and allocations


---

# 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.bio.xyz/bio/introduction/bio-protocol-v2/launcher.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.
