> For the complete documentation index, see [llms.txt](https://docs.alphafi.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alphafi.xyz/stsui-lst/the-stsui-standard.md).

# The stSUI Standard

#### What is the stSUI Standard?

An open-source framework for building liquid staking tokens on Sui. It defines how the contracts work — minting, redemption, validator delegation, fees, and DeFi features like flash staking.

Any team can use the Standard to launch their own LST.

#### Why a standard?

Most early LSTs are one-off designs. A standard means:

* New LSTs don't need to build from scratch.
* DeFi protocols can support multiple LSTs through one interface.
* Audits and security improvements carry across implementations.

#### What changed from SpringSUI

The Standard is forked from SpringSUI with three changes:

* **Multi-validator reward optimization.** Better suited for splitting stake across many validators.
* **Flash staking support.** Atomic stake-and-use flows in a single transaction.
* **Redistributable redemption fees.** Part of the redeem fee can go back to remaining stakers instead of the operator.

#### Custom LSTs on the Standard

Any team can deploy their own LST with their own:

* Validator set and weights
* Fee configuration
* Admin controls

stSUI is AlphaFi's configuration. Other teams can run different ones.


---

# 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:

```
GET https://docs.alphafi.xyz/stsui-lst/the-stsui-standard.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.