> 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.
Tezos delegation
What you delegate
The Account's full XTZ balance
Is your XTZ locked?
No. It stays liquid and you can transfer it at any time
Lock-up or bonding period
None
Time to undelegate
Immediate
**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 first reward takes several days.** Tezos counts time in **cycles**. A new delegation counts for the baker only after 4 cycles, about 4 days. The baker then pays you on its own schedule, so the first payment arrives later. These figures are from the Octez documentation on [proof of stake](https://octez.tezos.com/docs/active/proof_of_stake.html) and [consensus](https://octez.tezos.com/docs/active/consensus.html), checked on 9 October 2026.
After that delay, the payout 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.
### Risk
Tezos does not penalize a delegator when its baker misbehaves. Your XTZ stays under your control. Only staked XTZ is at risk, and Ledger Enterprise does not stake XTZ. This is from the [Tezos documentation on staking](https://docs.tezos.com/using/staking), checked on 9 October 2026.
## The reveal operation
Before a Tezos address can send its first operation, the network must know its public key. A **reveal** operation publishes the key. Tezos needs it once for each address.
The platform creates the reveal with the first operation that a new Account sends, for example its first transfer. The reveal is not a separate Request, and it needs no separate approval.
The reveal is a network operation, and the Account pays its fee. This is from the [Octez documentation on operations](https://octez.tezos.com/docs/active/blocks_ops.html), checked on 9 October 2026.
The interface does not name the reveal. On the Account's **Operations** tab, it shows with no type and no icon.
## One Request at a time
The interface allows **one** delegation Request per Account at a time. This is a Ledger Enterprise check, not a Tezos rule.
While a **Delegate** or **Undelegate** Request on the Account has not completed, you cannot start another. That covers a Request in any of these states:
* **Initiating...** (`INITIAL`)
* **Awaiting approval**, or **To review** for an Approver (`PENDING_APPROVAL`)
* **Processing...** (`EXECUTING`)
* **Stuck** (`STUCK`)
The button is disabled, and its tooltip explains why. For example: "You cannot delegate while a Tezos delegation request is already in progress for this account."
Once a delegation exists, the interface hides **Delegate**. The only action on the position is **Undelegate**. To move to a different baker in the interface:
1. Select **Undelegate** on the position.
2. Wait for that Request to complete.
3. Select **Delegate**.
4. Select the new baker.
> **Important:** Each delegation change is a Request, and needs approval like any other Request.
The API does not apply either restriction. See the [API documentation](https://help.enterprise.ledger.com/api-documentation-v2).
## 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 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/reference/networks/tezos.md?ask=&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.