> 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/comparison.md).

# Comparison

#### stSUI vs vSUI / haSUI / afSUI

| Feature         | stSUI          | vSUI / haSUI / afSUI |
| --------------- | -------------- | -------------------- |
| Unstaking       | Instant (1 tx) | Cooldown required    |
| Depeg risk      | Lower          | Higher               |
| Reward model    | Exchange rate  | Exchange rate        |
| Multi-validator | Yes            | Varies               |

The big difference is instant unstaking. With other LSTs, if the token drops below peg on a DEX, arbitrageurs can't redeem fast enough to close the gap. With stSUI, redemption is one transaction, so the peg holds tighter.

#### AlphaFi Staked SUI vs SpringSUI Ecosystem LSTs

AlphaFi Staked SUI is forked from SpringSUI. The differences:

| Feature                      | AlphaFi Staked SUI              | SpringSUI                   |
| ---------------------------- | ------------------------------- | --------------------------- |
| Multi-validator optimization | Yes                             | Originally single-validator |
| Flash staking                | Yes                             | Not in base framework       |
| Redemption fee               | Can be redistributed to stakers | Retained by operator        |

Same lineage, different focus. stSUI's additions are aimed at DeFi composability and aligning the operator with stakers.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.alphafi.xyz/stsui-lst/comparison.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.