> 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: enabling staking Rules, 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. The assets stay in your Account and under your governance. Staking and unstaking are Requests, approved exactly like transfers.

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

## Before you can stake

An Administrator must **enable staking Rules** on the Account and name who may create staking Requests and who approves them. Staking Rules are separate from send Rules: being able to send from an Account does not mean you can stake from it.

Where staking Rules are not enabled, the Account's staking section says so and points you at your Administrator. You cannot enable it yourself. See [**Creating and editing Accounts**](/help-center-v2/guides/accounts/creating-and-editing-accounts.md).

## Your positions

The Account's **Staking** tab is the whole picture:

<table><thead><tr><th width="191.47265625">Column</th><th>Meaning</th></tr></thead><tbody><tr><td>Validator</td><td>Who your assets are delegated to, with icon and name</td></tr><tr><td>Status</td><td>Whether that validator is currently active</td></tr><tr><td>Delegated amount</td><td>What is staked with them, in the asset and in countervalue</td></tr><tr><td>APY</td><td>The annual percentage yield for that position</td></tr><tr><td>Rewards earned</td><td>What the position has accrued</td></tr></tbody></table>

Positions list largest first. Staking more than once with the **same** validator combines the amounts into one row. A fully unstaked position disappears from the table.

The **Staked** figure in the Account's balances is the sum of all positions. Rewards are also totalled over all time, the past month, and the past week.

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

## Stake

1. Start staking from the staking section, or add to an existing position. The action is available when the Account has funds.
2. **Choose a validator.** Ledger's validator is pre-selected. You can search and pick any validator, each shown with icon, name, and net APY.
3. **Enter an amount.** The field shows the network's minimum, with the countervalue updating as you type. Amounts below the minimum, above your available balance, or otherwise invalid are rejected before you can continue.
4. **Check the fee.** It appears once there is an amount, in the network's asset and in countervalue, and can be refreshed.
5. **Add a note.** It is the only context your Approvers have.
6. **Review on your device** and confirm the details there.

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

### Warnings before you commit

The platform checks the Request before the device review and may ask you to acknowledge:

* **Fees may not be covered.** The Account may not hold enough native asset to pay them.
* **Other pending Requests may be affected.** Committing these funds may starve a Request already awaiting approval.
* **The chain state may not allow it.** The network may reject the operation as constructed.

Each lets you go back and edit, or accept and proceed. They are warnings, not blocks.

## Unstake

1. Use the unstake action on the position you want to reduce. **On some networks this action is called Withdraw**: see your network's page.
2. The validator is filled in for you, with its balance, and cannot be changed. Unstaking always targets one specific position.
3. Enter the amount, with its countervalue.
4. Check the fee, refreshing if needed.
5. Add a note if useful.
6. Review on your device.

The same pre-commit warnings apply.

**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.

## Where staking is available

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

## Related

* [**How governance works**](/help-center-v2/concepts/how-governance-works.md)
* [**Creating and editing Accounts**](/help-center-v2/guides/accounts/creating-and-editing-accounts.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/guides/staking.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.