# Launch Timeline

The launch will roll out in several key phases, as outlined below.

<figure><img src="/files/wZ2XD9QcknhSJXJZRBXZ" alt=""><figcaption></figcaption></figure>

### **July 14**

**Public Preview and Early-Access Registration**

* The first 3,000 users to join the waitlist receive a 1.1x multiplier on their foundational Firelight Points.&#x20;
* Join the waitlist to earn FlameBearer status and exclusive access to Alpha-Lab.

### Q4 2025:

**Phase 1 — LIVE**

* &#x20;The initial launch will feature a Firelight Launch Vault.&#x20;
* During this phase, only FXRP deposits will be accepted. Users can bridge XRP to the Flare Network via FAssets, minting FXRP — a trust-minimized, XRP-pegged asset.
* Once FXRP is staked on Firelight, users receive *stXRP*, a Liquid Staking Token (LST) that represents their proportional allocation in the Launch Vault. stXRP is issued at a 1:1 exchange rate with FXRP deposits.&#x20;
* There are zero slashing risks during this introductory period, ensuring a secure environment for early adopters.

### 2026

**Phase 2: Feature-Complete Launch — LIVE**

* Tokens deployed on Firelight support protocol coverage. Holders stake assets through a DeFi cover staking layer, where funds are programmatically secured in non-custodial DeFi cover vaults.
* DeFi cover policies are registered on-chain, allowing third parties to securely purchase coverage through an agent.
* Protocols can integrate on Firelight and offer on-chain coverage for technical events and economic events with clear triggers and attestations.
* Firelight covers smart contract risk, economic risk, oracle risk, and bridge risk.&#x20;


---

# 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.firelight.finance/introducing-firelight/launch-timeline.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.