# SUI (staking)

SUI is a supported network on Webapp 2.0. Sending, receiving, and account management follow the generic [Operator](/helpcenter2/for-operators/operators-overview.md) and [Administrator](/helpcenter2/overview.md) guides. The one area with SUI-specific behaviour is **staking**, covered below. (SUI also supports native tokens; see the short note at the end.)

{% hint style="info" %}
SUI was the first network to offer staking on Webapp 2.0, so it set the pattern the generic [Staking](/helpcenter2/for-operators/staking.md) page describes. That page covers the shared mechanics (the staking section, rewards display, fees, and approvals); this page covers what's specific to SUI.
{% endhint %}

## Before you can stake

An Administrator enables a **Staking ruleset** on the SUI account when [creating or editing it](/helpcenter2/creating-and-editing-accounts.md). For SUI, the staking ruleset uses multi-authorization rules (initiators and approval steps). An **Operator must be part of that ruleset** to stake or unstake; if staking isn't enabled, the account's Staking section shows a prompt to ask an Administrator to enable it. See [Governance rules & whitelists](/helpcenter2/governance-rules-and-whitelists.md).

## Stake SUI

From the SUI account's **Staking positions** section, choose **Start staking** (or **Add** for a further position), then:

* **Pick a validator.** The **Ledger validator** is pre-selected, and you can search a list of validators. Each shows its icon, name, and **Net APY** (the validator's APY minus its commission).
* **Enter an amount.** The **minimum stake is 1 SUI**. The USD countervalue and the network fee (in SUI) are shown, with the fee refreshing as you go.
* **Add an optional note**, then review on your Physical Security Device (PSD) like any other request.

A new stake starts as **Activating** and becomes **Active** at the start of the next epoch (an epoch is roughly one day); rewards accrue once the position is active.

{% hint style="info" %}
You can hold several positions. Staking to a **new validator** creates a new position; staking again to a **validator you already use** is added to that existing position. The positions table lists each one with its validator, status, delegated amount, APY, and rewards earned.
{% endhint %}

## Unstake SUI

Unstaking targets a **specific staking position**, and you can withdraw **part or all** of it. Once the transaction confirms on-chain, the unstaked SUI (together with its rewards) becomes **available to transact with immediately**; there's no unbonding or waiting period. A position that's fully unstaked disappears from the positions table.

{% hint style="info" %}
Rewards are realised when you unstake. SUI calculates and pays out a position's rewards as part of the unstake, so there's no separate claim step. An estimate of the rewards earned is shown against each position in the meantime.
{% endhint %}

## SUI addresses and native tokens

SUI addresses are 32-byte hexadecimal strings (for example `0x13d7...4a8f`). Verify a receive address on your PSD as described in [Receiving assets](/helpcenter2/for-operators/receiving-assets.md).

SUI also supports **native tokens**. Sending a token uses the standard [send flow](/helpcenter2/for-operators/sending-assets.md) with the token selected; the network fee is still paid in SUI. Unlike Solana and Hedera, SUI tokens don't require a separate token account to be created or activated first.

## Related

* [Staking](/helpcenter2/for-operators/staking.md): the generic staking section this page builds on.
* [Sending assets](/helpcenter2/for-operators/sending-assets.md) and [Receiving assets](/helpcenter2/for-operators/receiving-assets.md).


---

# Agent Instructions: 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://help.enterprise.ledger.com/helpcenter2/network-specific-guidance/sui-staking.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.