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

# Tezos (XTZ)

Tezos on Ledger Enterprise: how delegation works, and why your XTZ stays available while it is delegated.

## How Tezos differs

Tezos uses an **Account** model, like Ethereum. Two things set it apart in this product.

**Blocks are produced by bakers.** A **baker** is a validator on Tezos. Bakers put up their own XTZ as security, produce blocks, and receive the network's rewards. You do not become a baker. You **delegate** to one, and the baker shares its rewards with you.

**Storage on Tezos is paid for by burning XTZ.** Sending to an unallocated destination, meaning an empty or new address, costs a one-time **allocation fee**. It is a burn, not a fee paid to anybody, and it applies once per destination.

For the protocol itself, see the [Tezos documentation](https://docs.tezos.com/).

## Token coverage

Ledger Enterprise supports **XTZ only** on Tezos.

## What is out of scope

| Not supported  | Detail                                                                         |
| -------------- | ------------------------------------------------------------------------------ |
| Native staking | `STAKE`, `UNSTAKE` and `FINALIZE_UNSTAKE`, frozen funds, and Adaptive Issuance |
| Non-XTZ assets | FA1.2 and FA2 tokens                                                           |

Staking here means **classic delegation to a baker**, not the native staking introduced by the Paris protocol.

## Delegation

Delegating XTZ does not move it. Your balance stays in your Account and stays spendable.

<table><thead><tr><th width="235.78515625"></th><th>Tezos delegation</th></tr></thead><tbody><tr><td>What you delegate</td><td>The Account's <strong>full XTZ balance</strong></td></tr><tr><td>Is your XTZ locked?</td><td>No. It stays liquid and you can transfer it at any time</td></tr><tr><td>Lock-up or bonding period</td><td>None</td></tr><tr><td>Time to undelegate</td><td>Immediate</td></tr></tbody></table>

**You do not choose an amount.** Delegation applies to everything in the Account. XTZ that arrives later is included automatically.

Undelegating stops the delegation for the Account. Your XTZ stays where it was throughout.

> **Note:** Because the balance stays liquid, you can send XTZ while it is delegated. You do not have to undelegate first.

### How rewards are paid

**The chain pays your baker. Your baker then pays you.**

There is nothing to claim. The reward arrives as a payment from the baker into your Account.

The timing is the baker's decision, not the network's and not Ledger's. Bakers differ in how often they pay out and in what commission they keep. Some pay weekly, some per cycle, some less often.

> **Important:** A delegation that produces nothing for a long period usually means the baker is not paying out, not that the delegation failed. Check the baker's own published policy.

## One Request at a time

Tezos allows **one** delegation Request per Account at a time.

While a delegation or undelegation Request is waiting for approval, you cannot start another on that Account. The action is unavailable and explains why.

> **Important:** A delegation change needs approval like any other Request. If you want to move to a different baker, wait for the first Request to complete before you start the second.

## Related

* [**Staking**](/help-center-v2/guides/staking.md)
* [**Finding Accounts and balances**](/help-center-v2/guides/accounts/finding-accounts-and-balances.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/tezos.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.