# Genesis Allocation Mechanics

Genesis Launches use a dynamic tiered raise structure, where the raise size expands automatically based on total points pledged and $VIRTUAL committed.

* Raise thresholds are 21,000, 42,000, and 100,000 $VIRTUAL.
* If pledges surpass a threshold, the raise expands to the next tier.
* Any contributions beyond the highest threshold are automatically refunded.

Each participant’s allocation is determined by their relative points pledged, subject to a maximum commitment of 566 $VIRTUAL per wallet.

***

## How it Works

Each Genesis Launch follows this flow:

1. Users pledge points to access the presale.
2. The system calculates an estimated allocation based on total points pledged across all users.
3. Users are prompted to commit $VIRTUAL to match the estimated cost of their maximum allocation potential (determined by the amount of points they pledge).
4. When total pledges hit a threshold, the raise moves up to the next tier.
5. Final raise size is locked at the highest tier reached during the 24-hour window.

This creates a live, transparent coordination environment where allocation size reflects user engagement.

***

## Key Rules

| Parameter                         | Value                                             |
| --------------------------------- | ------------------------------------------------- |
| Max user allocation               | 566 $VIRTUAL (incl. 1% tax)                       |
| Max $VIRTUAL commitment per entry | 566 $VIRTUAL (incl. 1% tax)                       |
| Allocation logic                  | Based on points pledged relative to total pool    |
| Refunds                           | Unused $VIRTUAL and points automatically refunded |

If a user pledges more points than others, they will receive a proportionally larger share of the Genesis supply, capped by the per-wallet commitment limit of 566 $VIRTUAL.

Users must commit the calculated amount of $VIRTUAL at the same time as pledging points. If either is insufficient, the system will not accept the entry.

When total pledges pass a threshold, the raise moves up (21K → 42K → 100K). The final raise is locked at the highest tier reached within 24 hours.

Any unused $VIRTUAL is automatically refunded, including (a) if your final allocation is smaller than your commitment, and (b) any amount above the final raise tier reached.

***

## Real-Time Feedback

The Genesis interface displays:

* Total points pledged across the pool
* Leaderboard showing top participants
* Total $VIRTUAL committed
* Estimated allocation range based on current values
* Current raise tier and thresholds

***

## Dynamic Adjustment Window

Allocations are dynamic and adjust as new participants enter the pool during the 24-hour presale.

* If additional users pledge points, your estimated allocation may decrease.
* As aggregate pledges increase, the total raise may move into a higher tier (21K → 42K → 100K), unlocking a larger allocation pool. Once a pledge is submitted, it is locked and cannot be reduced or withdrawn. Participants may add additional pledges during the 24-hour presale window, but cannot adjust or remove existing commitments. Any pledges above the maximum cap of the highest tier are automatically refunded.
* Participants can increase their points and $VIRTUAL commitments at any time before the window closes.

{% hint style="danger" %}
If you wish to avoid dilution in your final allocation, you may submit additional pledges of points and $VIRTUAL during the presale. Once a pledge is made it is locked and cannot be reduced or withdrawn, but participants can add more at any time within the 24-hour window.
{% endhint %}

This structure encourages early and engaged participation, while preserving flexibility throughout the presale lifecycle.

***

## Tokenomics Structure

Each Genesis Launch follows a standardized token allocation framework:

| Component                    | Allocation (%) |
| ---------------------------- | -------------- |
| Presale                      | 7%             |
| Liquidity Pool (LP)          | 6%             |
| Airdrop to veVIRTUAL Holders | 2%             |
| Dev / Treasury / Marketing / | 85%            |

***

## FDV Structure:  Pledge vs. Market

In every Genesis launch, two FDVs (Fully Diluted Valuations) are defined by design: one during the pledge phase and another at the moment of market deployment. Each serves a distinct role in the lifecycle of an agent.

### Genesis Pledge FDV: Dynamic (Tier-Based)

During the 24-hour pledge window, Virgens contribute points and $VIRTUAL in exchange for 7% of the total token supply.

This sets an implied pre-launch FDV that depends on the final tier reached:

* Tier 1 (21,000 $VIRTUAL pledged): 21,000 ÷ 0.07 = 300,000 $VIRTUAL FDV
* Tier 2 (42,000 $VIRTUAL pledged): 42,000 ÷ 0.07 = 600,000 $VIRTUAL FDV
* Tier 3 (100,000 $VIRTUAL pledged): 100,000 ÷ 0.07 = 1,428,571 $VIRTUAL FDV

Rules:

* If Tier 1 (21,000 $VIRTUAL) is not reached, the launch is canceled and all funds and points are fully refunded.
* If pledges exceed Tier 2 (42,000 $VIRTUAL) but do not reach Tier 3 (100,000 $VIRTUAL), the pledge FDV is locked at Tier 2 (600k FDV).

### Market FDV: Fixed at 6% Float

Once the Genesis launch is successful, 6% of the total token supply is deployed into a liquidity pool, paired with the pledged $VIRTUAL.

This creates a market FDV that is always calculated against 6% supply, regardless of the tier:

* Tier 1 (21k): 21,000 ÷ 0.06 = 350,000 $VIRTUAL FDV
* Tier 2 (42k): 42,000 ÷ 0.06 = 700,000 $VIRTUAL FDV
* Tier 3 (100k): 100,000 ÷ 0.06 = 1,666,667 $VIRTUAL FDV

### Why This Matters:

This dual-FDV structure is intentional:

* Pledge FDV (7% supply): Rewards early conviction by allowing Virgens to enter at lower implied valuations.
* Market FDV (6% supply): Establishes a robust liquidity base from Day 1, ensuring smoother price discovery and market stability.

***


---

# 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://whitepaper.virtuals.io/builders-hub/genesis-launch/genesis-allocation-mechanics.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.