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

# Staking

How to stake and unstake on Ledger Enterprise: the Staking Rule, choosing a validator, and managing positions.

**Role: Operators.** Administrators can see an Account's staking positions but cannot start or end them, in the same way they cannot create transactions.

Staking delegates assets to a validator, which makes them eligible for network rewards. Staking and unstaking are Requests, approved exactly like transfers.

Where the staked assets sit depends on the network:

* **Hedera and Tezos:** the balance stays in your Account and stays spendable.
* **Sui and Ethereum:** the staked amount leaves the available balance. It shows under **Total staked** until you unstake or withdraw.

The flow below is shared across networks. Amounts, waiting periods, and the names of the actions vary, and those specifics are in [**Networks**](https://help.enterprise.ledger.com/help-center-v2/reference/networks.md).

## Before you can stake

A Master Administrator must add a Staking Rule to the Account, in its **Staking Rule** section. The Rule names who may create staking Requests and who approves them. One Rule covers both staking and unstaking. Staking Rules are separate from send Rules: being able to send from an Account does not mean you can stake from it.

Without a Staking Rule that lists you, **Start staking** is disabled. Its tooltip reads "You do not have permission to stake". You cannot add the Rule yourself. See [**Creating and editing Accounts**](https://help.enterprise.ledger.com/help-center-v2/guides/accounts/creating-and-editing-accounts.md).

## Your positions

The Account's **Staking** tab is the whole picture. On Sui, Hedera and Tezos, the **Staking positions** table has these columns:

<table><thead><tr><th width="191.47265625">Column</th><th>Meaning</th></tr></thead><tbody><tr><td>Validators</td><td>Who your assets are delegated to, with icon, name, a link to the explorer, and the validator's APY</td></tr><tr><td>Amount staked</td><td>What is staked with that validator</td></tr><tr><td>Rewards earned</td><td>What the position has accrued</td></tr><tr><td>Current value</td><td>The amount staked plus the rewards earned</td></tr><tr><td>Actions</td><td>The exit action for that position. Operators only</td></tr></tbody></table>

Ethereum has its own table, described in [**Ethereum**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/ethereum.md).

Positions list largest first. The table lists each position that the network reports, so two stakes with the same validator can show as two rows. A fully unstaked position disappears from the table.

Above the table, Sui and Hedera show **Total staked**, **Available balance**, **Total rewards** and **Total value**. Tezos shows only **Available balance**.

> **Important:** The APY shown is the validator's annual percentage yield before its commission. What you receive is lower by that commission. Yields vary and are not guaranteed by Ledger.

> **Note:** An **inactive** validator has stopped participating, and its rewards stop. Unstaking and delegating elsewhere restarts them.

## Stake

1. On the **Staking** tab, select **Start staking**. On Tezos, the button reads **Delegate**.
2. **Enter an amount.** The countervalue updates as you type. On Hedera and Tezos, the amount is the full balance and you cannot change it.
3. **Select a validator.** No validator is pre-selected. The list puts the largest total staked first, and shows each validator's icon, name, APY and total staked. On Tezos, the bakers that Ledger added for your Workspace come first, tagged **Your validator**.
4. **Add a note.** It is the only context your Approvers have.
5. **Check the fee.** The **Max fee** row appears once there is an amount and a validator. It updates when the inputs change.
6. Select **Review**.
7. Check the details on your Ledger device.
8. Approve the Request on your Ledger device.

On Ethereum, the form also asks for a provider and a number of validators. The list of providers comes from Ledger. See [**Ethereum**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/ethereum.md).

Through the API, an API user creates and approves staking Requests without the interface. See the [API documentation](https://help.enterprise.ledger.com/api-documentation-v2).

## Unstake

The exit action is **Unstake** on Sui and Hedera, **Undelegate** on Tezos, and **Withdraw** on Ethereum.

1. In the **Actions** column, select the exit action on the position you want to reduce.
2. The validator is filled in for you, with the current position, and cannot be changed. Unstaking always targets one specific position.
3. Enter the amount, with its countervalue. On Sui, **Max** fills in the whole position. On Hedera and Tezos, the amount is the whole position and you cannot change it.
4. Add a note if useful.
5. Check the **Max fee**.
6. Select **Review**.
7. Check the details on your Ledger device, and approve.

**How long until the assets are usable again depends on the network.** On some, the balance and rewards come back immediately. On others there is a waiting period. During that time the assets produce no rewards and cannot be moved. Check your network's page before you plan around it.

## Staking risks

Staking carries protocol risks that Ledger does not control. The validator runs the node, and the network applies its own rules to the validator.

* **Slashing.** Some networks penalize a validator that breaks the protocol rules, for example by signing two different blocks for the same slot. The penalty burns part of the staked assets, and the network can remove the validator.
* **Missed rewards.** A validator that is offline or performs badly receives fewer rewards, or none. The positions delegated to it then receive fewer rewards too.

Which risks apply, and to what, depends on the network. Each network page with staking states it, with a link to the network's own documentation.

The **Staking** tab has no slashed status. To check a validator's record, use the network's explorer.

## What can go wrong

* **Start staking is disabled.** The available balance is 0, or no Staking Rule lists you. On Ethereum, the button is also disabled below 32 ETH of available balance, or when no provider is available.
* **Start staking is missing on Hedera or Tezos.** A position already exists. These networks stake the whole balance, so there is one position for each Account.
* **The amount shows an error.** The amount is below the network minimum, for example "The minimum amount to stake is 1 SUI". The form shows the minimum only after you enter an amount.
* **The amount or the fee shows a warning.** On Sui, the amount plus the **Max fee** is above the available balance. On Hedera and Tezos, the **Max fee** is above it. The warning does not block the Request. On Ethereum, the form blocks it with "Amount and fee exceed your available balance".
* **A Transaction Check result needs your answer.** On Ethereum, the form screens the transaction with **Transaction Check**. If the check flags a risk or a threat, or cannot complete, select **Proceed** to continue. Select **Cancel** to stop.
* **The exit action is disabled.** Its tooltip reads "This position is pending on-chain confirmation." The network has not settled the position yet.

## Where staking is available

Staking is available on a subset of networks and the set grows. See [**Networks**](https://help.enterprise.ledger.com/help-center-v2/reference/networks.md) for what is supported and each network's specifics.

## Related

* [**How governance works**](https://help.enterprise.ledger.com/help-center-v2/concepts/how-governance-works.md)
* [**Creating and editing Accounts**](https://help.enterprise.ledger.com/help-center-v2/guides/accounts/creating-and-editing-accounts.md)
* [**Networks**](https://help.enterprise.ledger.com/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 by asking a question.

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

```
GET https://help.enterprise.ledger.com/help-center-v2/guides/staking.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.
