> For the complete documentation index, see [llms.txt](https://wp.refract.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp.refract.finance/introduction.md).

# Introduction

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

In the evolving landscape of Solana's decentralized finance (DeFi) ecosystem, staking has emerged as a foundational mechanism for securing the network and generating yield. However, the current staking and liquid staking landscape on Solana is highly fragmented. Each LST (Liquid Staking Token) platform operates in isolation, with its own validator sets, token standards, interfaces, and yield flows. This fragmentation creates friction for both users and developers, limiting composability, increasing complexity, and fragmenting liquidity.

**Refract** addresses this problem by introducing a unified, modular yield routing layer for Solana. It serves as the yield baseplate, a programmable interface that allows users to stake SOL, select a backend strategy, and mint branded LSTs such as `pxJITO`, `pxMNDE`, or `pxBLZE`. These tokens are directly tied to specific strategies or platforms, giving users more transparency, flexibility, and control over their staking allocations.

At its core, Refract transforms staking into a composable primitive. By abstracting validator selection, LST issuance, and strategy execution into a single contract layer, Refract enables seamless integration with other DeFi protocols, simplifies UX, and supports both retail and institutional use cases. Whether you want to farm, lend, bridge, or build on top of LSTs, Refract makes it possible, all from one unified interface.

This whitepaper outlines the architecture, functionality, and potential of Refract. It serves as both a technical overview and a vision for a more modular, accessible, and interoperable yield ecosystem on Solana.


---

# 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://wp.refract.finance/introduction.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.