> 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: capabilities per network, which networks and tokens a Workspace has, and recipient addresses.

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.

Some operations exist on a few networks only:

<table><thead><tr><th width="150">Network</th><th>Contract operations</th><th>Speed-up and Cancel</th><th>Transaction Check</th><th>Receive Rule</th></tr></thead><tbody><tr><td>Bitcoin (BTC)</td><td>No</td><td>Yes, Replace by Fee</td><td>No</td><td>No</td></tr><tr><td>Ethereum and EVM networks</td><td>Yes, interaction and deployment</td><td>Yes, Replace by Nonce, on sends only</td><td>Yes, except contract deployment</td><td>No</td></tr><tr><td>Sui, Hedera, Tron, Ripple, Stellar, Tezos</td><td>No</td><td>No</td><td>No</td><td>No</td></tr><tr><td>Canton (CC)</td><td>No</td><td>No</td><td>No</td><td>Yes, required</td></tr></tbody></table>

* **Contract operations** are contract interaction and contract deployment. Each has its own Rule. See [**Contract operations**](https://help.enterprise.ledger.com/help-center-v2/guides/transactions/contract-operations.md).
* **Speed-up and Cancel** replace a send transaction that is not yet confirmed. See [**Bitcoin**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/bitcoin.md#if-a-transaction-is-stuck) and [**Ethereum**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/ethereum.md#if-a-transaction-is-stuck).
* **Transaction Check** screens EVM sends, contract interactions and Ethereum staking operations. See [**Sending assets**](https://help.enterprise.ledger.com/help-center-v2/guides/transactions/sending-assets.md).
* **Receive Rule**: on Canton, accepting an incoming transfer is a Request under the Account's Receive Rule. See [**Canton**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/canton.md).

> **Important:** Canton works differently from every other network here, including how you receive funds. Read [**Canton**](https://help.enterprise.ledger.com/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. [**Ethereum**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/ethereum.md) lists the EVM networks that Ledger Enterprise supports. See [**Networks and tokens in your Workspace**](#networks-and-tokens-in-your-workspace).

## Networks and tokens in your Workspace

Ledger sets the list of networks enabled for each Workspace. This applies to every network family, not only to EVM networks. An Administrator cannot change the list.

* **Create Account** lists only the networks enabled for your Workspace.
* The API refuses to create an Account on a network that is not enabled.
* The platform refuses a new transaction Request on a network that is not enabled. This also applies to Accounts that already exist on that network.

So if Ledger disables a network for your Workspace, the Accounts on that network cannot start a new transaction.

**Tokens come from Ledger's asset catalog.** A token Account can exist only for a token that is in the catalog for its network. **Create Account** lists only those tokens, and the API refuses a token that is not in the catalog. On Canton, each token is also enabled per Workspace. See [**Canton**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/canton.md#token-coverage).

A token can reach a parent Account that has no token Account for it. It then shows as **View only**. See [**Tokens received without a token Account**](https://help.enterprise.ledger.com/help-center-v2/guides/accounts/finding-accounts-and-balances.md#tokens-received-without-a-token-account).

## Testnets

A **testnet** is a copy of a network that exists for tests. A testnet Account works like any other Account. It has the same Rules, and its Requests need the same approvals.

**Testnet assets have no market value.** The interface shows their countervalue as **N/A**.

Ledger enables testnets for a Workspace in the same way as other networks. The product supports these testnets:

<table><thead><tr><th width="190">Testnet</th><th>Network page</th><th>Staking</th></tr></thead><tbody><tr><td>Ethereum Hoodi</td><td><a href="https://help.enterprise.ledger.com/help-center-v2/reference/networks/ethereum.md#testnets">Ethereum</a></td><td>Yes</td></tr><tr><td>Ethereum Sepolia*</td><td><a href="https://help.enterprise.ledger.com/help-center-v2/reference/networks/ethereum.md#testnets">Ethereum</a></td><td>No</td></tr><tr><td>Sui Testnet</td><td><a href="https://help.enterprise.ledger.com/help-center-v2/reference/networks/sui.md#testnet">Sui</a></td><td>Yes</td></tr><tr><td>Bitcoin testnet4</td><td><a href="https://help.enterprise.ledger.com/help-center-v2/reference/networks/bitcoin.md#testnet">Bitcoin</a></td><td>No</td></tr></tbody></table>

\*Support of custom ERC-20 tokens on request.

## Recipient addresses

The send form checks the format of the recipient address for the network as you type. The recipient field shows an example address for the Account's network. The examples below are shortened, as in the form.

<table><thead><tr><th width="150">Network</th><th width="190">Example in the form</th><th>What to know</th></tr></thead><tbody><tr><td>Bitcoin (BTC)</td><td><code>bc1qar0srrr7…</code></td><td>Any valid Bitcoin address format. See <a href="https://help.enterprise.ledger.com/help-center-v2/reference/networks/bitcoin.md#sending-to-other-address-formats">Bitcoin</a></td></tr><tr><td>Ethereum and EVM networks</td><td><code>0x4F10eb44…</code></td><td>Every EVM network uses the same address format. Check the network of the Account before you send. See <a href="https://help.enterprise.ledger.com/help-center-v2/reference/networks/ethereum.md">Ethereum</a></td></tr><tr><td>Sui (SUI)</td><td><code>0x02a212de6a9d…</code></td><td></td></tr><tr><td>Hedera (HBAR)</td><td><code>0.0.1234567</code></td><td>A Hedera account ID: three numbers separated by dots. See <a href="https://help.enterprise.ledger.com/help-center-v2/reference/networks/hedera.md">Hedera</a></td></tr><tr><td>Tron (TRX)</td><td><code>TR7NHqjeKQxG…</code></td><td>You cannot send TRX to the Account's own address. See <a href="https://help.enterprise.ledger.com/help-center-v2/reference/networks/tron.md">Tron</a></td></tr><tr><td>Ripple (XRP)</td><td><code>rEb8TK3gBgk5…</code></td><td>The destination tag has its own field. You cannot send to the Account's own address. See <a href="https://help.enterprise.ledger.com/help-center-v2/reference/networks/ripple.md">Ripple</a></td></tr><tr><td>Stellar (XLM)</td><td><code>GAAZI4TCR3TY…</code></td><td>The memo has its own field. See <a href="https://help.enterprise.ledger.com/help-center-v2/reference/networks/stellar.md">Stellar</a></td></tr><tr><td>Tezos (XTZ)</td><td><code>tz1VSUr8wwNh…</code></td><td></td></tr><tr><td>Canton (CC)</td><td><code>alice::1220a1b2c3…</code></td><td>A party ID. See <a href="https://help.enterprise.ledger.com/help-center-v2/reference/networks/canton.md">Canton</a></td></tr></tbody></table>

These messages can show under the recipient field:

<table><thead><tr><th width="300">Message</th><th>Meaning</th></tr></thead><tbody><tr><td>Recipient is required</td><td>The field has no address</td></tr><tr><td>Must be a valid address for the selected asset</td><td>The address does not have the format of the Account's network</td></tr><tr><td>You cannot send to this Account's own address</td><td>Ripple, and TRX on Tron, only. The recipient is the address of the sending Account</td></tr></tbody></table>

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

Bitcoin and the EVM networks offer a choice of fee strategies, from slower and cheaper through to faster, plus a custom option. The other networks have no speed choice.

## Staking, in general

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

The flow is shared. A Master Administrator adds a Staking Rule to the Account. An Operator named in that Rule then stakes with a validator. See [**Staking**](https://help.enterprise.ledger.com/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 are not instant: a partial withdrawal usually takes hours, and a full exit a little over a day</td></tr></tbody></table>

## Related

* [**Sending assets**](https://help.enterprise.ledger.com/help-center-v2/guides/transactions/sending-assets.md)
* [**Staking**](https://help.enterprise.ledger.com/help-center-v2/guides/staking.md)
* [**Limits**](https://help.enterprise.ledger.com/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 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.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.
