> For the complete documentation index, see [llms.txt](https://docs.firelight.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.firelight.finance/for-stakers/emission-mechanics.md).

# Emission Mechanics

Stakers earn from two sources: the base rate emissions on stXRP, and protocol-related rewards funded by protocol emissions boosts. This page explains how each accrues and how Firelight Points fit in.

| Source                   | What it is                                              | How it accrues                                                                       |
| ------------------------ | ------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| Base rate emissions      | The native staking rate on stXRP from coverage premiums | Accrues into the vault, raising the position's redemption value                      |
| Protocol-related rewards | Rewards funded by protocol emission boosts              | Protocol emission boosts are distributed outside of the vault to directly to stakers |

### How coverage premiums accrue

Settled premiums stream into the vault on a regular cadence rather than as a single period-end distribution, so a deployment made mid-period begins earning shortly after deployment. Premiums are converted into the vault's collateral asset and compound into the redemption value.

### Protocol-related rewards

In addition to auto-compounding coverage premiums, stakers can receive emission boosts for participation. Protocol-related rewards are claimable rather than auto-compounded.

### Firelight Points

Firelight Points carry over from Phase 1 into the coverage phase. They accrue based on the amount staked and the time held, and run alongside the base rate emissions and other rewards above as a loyalty and engagement measure. They are not a claim on premiums.

#### **How points are calculated**

Your Firelight Points are determined by three factors: the total amount of stXRP you hold (both in your wallet and deployed in DeFi protocols), the length of time you hold it, and your Boost. Balances are snapshotted hourly on the last block of each hour, and points accrue for every fully completed hour.

$$
\text{Firelight Points} =
\left(
\text{stXRP}*{\text{held}} +
\text{stXRP}*{\text{DeFi}}
\right)
\times
\text{Time}\_{\text{held}}
\times
\text{weightedBoost}
$$

**weightedBoost** is determined by the different boosts assigned to holding stXRP and the different boosts assigned to DeFi deployments of stXRP. The calculation runs continuously, rewarding consistent participation in the ecosystem.

### What stakers see in practice

1. Stake FXRP and receive stXRP as a vault position.
2. The position's redemption value rises continuously as base rate emissions accumulate.
3. Firelight Points accrue based on amount and duration staked.
4. To exit, initiate an unstake (redeeming your stXRP and ending emissions accrual), wait for the unstaking window to end at the close of the following cover period, then withdraw the underlying FXRP.

### Where to read next

* [Risk and Exposure](/for-stakers/risk-and-exposure.md) covers the other side of the return profile, plus capacity and leverage.
* [Deployments and Withdrawals](/for-stakers/deployments-and-withdrawals.md) covers what accrues during an active position.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.firelight.finance/for-stakers/emission-mechanics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.