> For the complete documentation index, see [llms.txt](https://help.enterprise.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.enterprise.ledger.com/help-center-v2/reference/networks/sui.md).

# Sui (SUI)

Sui on Ledger Enterprise: the minimum stake, validator choice, and how quickly unstaked assets return.

## How Sui differs

Sui stores everything as an **object**. Each object has its own identifier, its own type, and an owner. Your coins are objects. A staking position is an object too.

This is a third model, distinct from the two most readers already know:

| Model              | How a balance is held                         |
| ------------------ | --------------------------------------------- |
| Bitcoin, UTXO      | A set of unspent outputs, carrying value only |
| Ethereum, Accounts | A number recorded against an address          |
| Sui, objects       | Typed objects, each owned by an address       |

One consequence shows up in this product. A staking position is a single object, so it cannot be partly withdrawn. Sui splits the object in two instead, and returns one part.

For the protocol itself, see the [Sui documentation](https://docs.sui.io/).

## Token coverage

Ledger Enterprise supports **SUI and Sui tokens**.

A Sui token is not a contract, as it would be on Ethereum. It is a native object type, identified by its **coin type**. There is no token standard to check against, because tokens are part of the protocol.

A token Account holds one coin type, and attaches to a parent Account.

## Staking

<table><thead><tr><th width="225.17578125">Detail</th><th>Value</th></tr></thead><tbody><tr><td>Minimum stake</td><td><strong>1 SUI</strong></td></tr><tr><td>Exit action</td><td>Unstake</td></tr><tr><td>Return after unstaking</td><td><strong>Immediate</strong></td></tr></tbody></table>

### Choosing a validator

You can search the full list and pick any validator, each shown with its icon, name, and net annual percentage yield (APY).

**Net APY is the yield after the validator's commission**, which is what you actually receive. Compare validators on that figure. Yields vary and are not guaranteed by Ledger.

Staking more than once with the same validator combines the positions into a single row rather than listing them separately.

A validator that becomes inactive stops producing rewards. Unstaking and delegating elsewhere restarts them.

### How rewards are paid

**Rewards are not paid out as separate transfers.** No incoming transaction arrives, and there is nothing to claim.

A Sui **epoch** lasts 24 hours. At each epoch boundary the staking pool's exchange rate appreciates, so your position grows in place.

A stake accrues rewards only for the epochs it was active for in full. A position opened part way through an epoch accrues nothing for that epoch.

You see the accumulated reward when you unstake. Principal and reward return together.

### Unstaking

**Your balance and rewards come back immediately.** There is no waiting period. Once the unstake Request is approved and executed, you can send the assets.

You can unstake part of a position. Sui does this by splitting the position in two, then returning one part. **Both parts must keep more than 1 SUI.**

So from a 10 SUI position you can unstake:

* Any amount from 1 to 9 SUI, which leaves the rest staked
* The full 10 SUI, which closes the position

You cannot unstake 9.5 SUI from a 10 SUI position, because that would leave 0.5 SUI staked.

## Related

* [**Staking**](/help-center-v2/guides/staking.md)
* [**Networks**](/help-center-v2/reference/networks.md)


---

# 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://help.enterprise.ledger.com/help-center-v2/reference/networks/sui.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.