# $ROOM Token Launch

### Genesis Pre-Sale

Each Virtuals 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. Final allocation is determined at the end of the 24-hour window, relative to total points pledged.

* Max user allocation: 0.5% of token supply
* Max $Virtual/Entry: 566 $VIRTUAL (incl. 1% tax)
* Allocation logic: Based on points pledged relative to the total pool
* Refunds: Unused $VIRTUAL and points automatically refunded<br>

Date: June 17th, 2025 - 3PM UTC \
Duration: 24 hours

For more details about the Genesis mechanics, please refer to the Virtuals [docs](https://whitepaper.virtuals.io/about-virtuals/tokenization-platform/genesis-launch/genesis-allocation-mechanics).

### Community Sale

Built on community-driven principles, Backroom empowers users and supporters to participate more deeply across ecosystems — including, but not limited to, Virtuals Virgens.

The Community Sale is a blind-price discovery event: the token allocation is fixed at 8%, while the FDV will be determined by the total amount raised.

* Requirements: Open for everyone to join
* Allocation: 8% of the total token supply (fixed)
* Min./Max $ETH/user Min. 0.05 ETH, max. 5 ETH
* If hard cap isn’t reached - more tokens per user
* Number of entries: One
* Distribution: Claimable, without tax or slippage

\
Date: June 18th, 2025 (detailed Time TBA) \
Duration: 24 hours

\
\*updated June 17


---

# 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.backroom.tech/getting-involved/interactive-blocks.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.