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

# Networks

Reference for each network supported on Ledger Enterprise, and which capabilities are available per network.

The guides apply to every network. These pages gather what is specific to one: address types, fee behavior, staking terms and minimums, and tokens.

**If your network has no page here, the guides are complete for it.**

## Capabilities by network

<table><thead><tr><th width="150">Network</th><th width="110">Tokens</th><th width="115">Staking</th><th width="150">Message signing</th><th>Notes</th></tr></thead><tbody><tr><td>Bitcoin (BTC)</td><td>No</td><td>No</td><td>Yes, BIP-137</td><td>Native SegWit for new Accounts, unspent outputs visible</td></tr><tr><td>Ethereum and EVM networks</td><td>Yes</td><td>Ethereum (ETH) only</td><td>Yes, EIP-191 and EIP-712</td><td>Linked Accounts, contract operations</td></tr><tr><td>Sui (SUI)</td><td>Yes</td><td>Yes (SUI)</td><td>No</td><td>Immediate return when unstaking</td></tr><tr><td>Hedera (HBAR)</td><td>Yes</td><td>Yes (HBAR)</td><td>No</td><td>Account activation before first use</td></tr><tr><td>Tron (TRX)</td><td>Yes (TRC-20)</td><td>No</td><td>No</td><td>Bandwidth and energy instead of a plain fee</td></tr><tr><td>Ripple (XRP)</td><td>No</td><td>No</td><td>No</td><td>Destination tags</td></tr><tr><td>Stellar (XLM)</td><td>No</td><td>No</td><td>No</td><td>Memos, in four types</td></tr><tr><td>Tezos (XTZ)</td><td>No</td><td>Yes (XTZ)</td><td>No</td><td>Delegation covers the whole balance and stays liquid</td></tr><tr><td>Canton (CC)</td><td>Yes (CIP-0056, on Request)</td><td>No</td><td>No</td><td>Incoming transfers must be accepted, and can be auto-accepted for a period</td></tr></tbody></table>

Every network page carries a **Token coverage** section stating exactly which assets that network supports here.

> **Important:** Canton works differently from every other network here, including how you receive funds. Read [**Canton**](/help-center-v2/reference/networks/canton.md) before using a Canton Account.

Which EVM networks your Workspace has is set up for you, so the list varies. Ask your Administrator if a network you expect is missing.

## Fees, in general

Every network prices fees differently, but the platform treats them the same way: **the figure you authorize is a maximum**, not a prediction. The network usually takes less and the difference is not deducted. If the network requires more than the ceiling at execution, the transaction fails with a fee error rather than costing more than you approved.

Networks offering a choice of speed present fee strategies, from slower and cheaper through to faster, plus a custom option.

## Staking, in general

Staking is available on **Sui**, **Hedera**, **Ethereum**, and **Tezos**.

The flow is shared. An Administrator enables staking Rules, then an Operator delegates to a validator. See [**Staking**](/help-center-v2/guides/staking.md).

The details differ by network:

<table><thead><tr><th width="148.70703125">Network</th><th>What is different</th></tr></thead><tbody><tr><td>Sui</td><td>Unstaking returns your assets immediately</td></tr><tr><td>Hedera</td><td>You stake the whole Account balance. Unstaking is instant</td></tr><tr><td>Tezos</td><td>Delegation covers the whole balance. Your XTZ stays spendable throughout</td></tr><tr><td>Ethereum</td><td>Staking works in whole validators. Withdrawals take at least a day</td></tr></tbody></table>

## Related

* [**Sending assets**](/help-center-v2/guides/transactions/sending-assets.md)
* [**Staking**](/help-center-v2/guides/staking.md)
* [**Limits**](/help-center-v2/reference/limits.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.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.