> For the complete documentation index, see [llms.txt](https://reflex-protocol.gitbook.io/reflex-protocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://reflex-protocol.gitbook.io/reflex-protocol-docs/what-is-reflex.md).

# What is Reflex?

Reflex lets pump.fun token holders stake their tokens and earn SOL.

When a token creator redirects their pump.fun creator fees to the staking pool, those fees get distributed to stakers as SOL rewards. No middleman. No platform cut. 100% goes to stakers.

Holders lock their tokens, earn shares proportional to how much they staked and how long they committed, and claim SOL whenever they want.

## Why does this matter?

Every pump.fun token has the same lifecycle. It launches, people buy in, the chart goes up, then the first sellers trigger a cascade and everyone who held gets burned. There's no reason to hold.

Reflex changes the incentive. Locked tokens can't dump. And when they're earning real SOL, there's a reason to keep them locked.

## SOL, not tokens

Most staking protocols pay you in the same token you staked. That's inflationary — the supply is just expanding and you're not actually earning anything new.

Reflex rewards come from real trading activity on pump.fun. When people trade the token, the creator earns fees, and those fees flow through to stakers as SOL. That's actual yield.

## The loop

{% stepper %}
{% step %}

### Pool gets created

Anyone can create a staking pool for any pump.fun token. Permissionless.
{% endstep %}

{% step %}

### Creator redirects fees

The token creator points their pump.fun creator fee sharing to the pool's SOL vault address.
{% endstep %}

{% step %}

### SOL goes to token stakers

Fees are distributed to stakers as SOL rewards every 5 minutes.
{% endstep %}

{% step %}

### Holders stay, more volume, more fees

Locked tokens reduce selling pressure, encouraging holders to stay and generating more trading volume and fees.
{% endstep %}
{% endstepper %}


---

# 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://reflex-protocol.gitbook.io/reflex-protocol-docs/what-is-reflex.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.