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
Bitcoin (BTC)
No
No
Yes, BIP-137
Native SegWit for new Accounts, unspent outputs visible
Ethereum and EVM networks
Yes
Ethereum (ETH) only
Yes, EIP-191 and EIP-712
Linked Accounts, contract operations
Sui (SUI)
Yes
Yes (SUI)
No
Immediate return when unstaking
Hedera (HBAR)
Yes
Yes (HBAR)
No
Account activation before first use
Tron (TRX)
Yes (TRC-20)
No
No
Bandwidth and energy instead of a plain fee
Ripple (XRP)
No
No
No
Destination tags
Stellar (XLM)
No
No
No
Memos, in four types
Tezos (XTZ)
No
Yes (XTZ)
No
Delegation covers the whole balance and stays liquid
Canton (CC)
Yes (CIP-0056, on Request)
No
No
Incoming transfers must be accepted, and can be auto-accepted for a period
Every network page carries a Token coverage section stating exactly which assets that network supports here.
Some operations exist on a few networks only:
Bitcoin (BTC)
No
Yes, Replace by Fee
No
No
Ethereum and EVM networks
Yes, interaction and deployment
Yes, Replace by Nonce, on sends only
Yes, except contract deployment
No
Sui, Hedera, Tron, Ripple, Stellar, Tezos
No
No
No
No
Canton (CC)
No
No
No
Yes, required
Contract operations are contract interaction and contract deployment. Each has its own Rule. See Contract operations.
Transaction Check screens EVM sends, contract interactions and Ethereum staking operations. See Sending assets.
Receive Rule: on Canton, accepting an incoming transfer is a Request under the Account's Receive Rule. See Canton.
Important: Canton works differently from every other network here, including how you receive funds. Read Canton before using a Canton Account.
Which EVM networks your Workspace has is set up for you, so the list varies. Ethereum lists the EVM networks that Ledger Enterprise supports. See 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.
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.
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:
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.
Ethereum and EVM networks
0x4F10eb44…
Every EVM network uses the same address format. Check the network of the Account before you send. See Ethereum
Sui (SUI)
0x02a212de6a9d…
Ripple (XRP)
rEb8TK3gBgk5…
The destination tag has its own field. You cannot send to the Account's own address. See Ripple
Tezos (XTZ)
tz1VSUr8wwNh…
These messages can show under the recipient field:
Recipient can't be empty
The field has no address
This recipient address is not valid for the selected asset
The address does not have the format of the Account's network
You can't send to this account's own address
Ripple, and TRX on Tron, only. The recipient is the address of the sending Account
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.
The details differ by network:
Sui
Unstaking returns your assets immediately
Hedera
You stake the whole Account balance. Unstaking is instant
Tezos
Delegation covers the whole balance. Your XTZ stays spendable throughout
Ethereum
Staking works in whole validators. Withdrawals are not instant: a partial withdrawal usually takes hours, and a full exit a little over a day
Related
Last updated