Limits
The limits that apply to names, notes, Rules, approval steps, staking and minimum balances on Ledger Enterprise, in the interface and in the API.
Names and text
Where a limit differs between the interface and the API, the table gives both. In the interface, Account, Policy, Whitelist, group, user and Portfolio names accept ASCII characters only. The API does not check that.
For Accounts, Policies, Whitelists, groups and users, a unique name must also differ from the names that pending create or edit Requests hold.
Account name
45 characters, unique in the Workspace
Policy name
45 characters, unique in the Workspace
Whitelist name
45 characters, unique in the Workspace
Whitelist entry label
50 characters
Whitelist entry address
200 characters
Group name
45 characters, unique in the Workspace
User name
19 characters in the interface, 45 in the API. Unique among active users and pending registrations
Portfolio name
45 characters in the interface, 120 in the API. Unique among active Portfolios, with no difference between upper and lower case
Note
1,000 characters in the interface, on the forms that offer a note: operations and Whitelists. Through the API, a note has a title and a content, with no length limit, and any Request can carry one
Rules per Account
Rules are set per operation type. Which ones you can add depends on the asset.
Send
All assets
Yes
4
Yes
Yes
Receive
Canton only
Yes, on Canton
1
No
No
Stake
Assets that support staking
No
1
No
No
Sign message
Assets that support it
No
1
No
No
Contract interaction
EVM networks
No
1
Yes
Yes
Contract deployment
EVM networks
No
1
Yes
No
Token activation
No supported asset today
No
1
No
No
The interface enforces the Required and Max Rules columns, and the operation types of the asset. The API does not check them. It accepts any number of Rules for each operation type, and it does not require a Send Rule.
A token Account takes Send Rules only, plus a Receive Rule on Canton.
Send Rules are checked in order. The first Rule that matches the amount, the destination Whitelist and the user who creates the transfer is the one that applies. See Send Rules.
Note: A Receive Rule only exists on Canton, because Canton is the only network where receiving is an action that needs approval. See Canton.
Approval steps
A step names one group or a list of Operators, never both.
Interface
From 1 to one less than the step's number of members. A step with one member has a quorum of 1
API
From 1 to the step's number of members
An edit that leaves a group with fewer members than the quorum of a step that uses it is rejected.
Whitelists
Each entry is tied to one currency. There are no multi-currency entries.
There is no maximum number of addresses in a Whitelist, and the platform enforces no ceiling.
As a recommendation only: an edit larger than about 90 addresses is hard for Approvers to review on a Ledger device. Nothing stops you exceeding it.
Staking
Minimums and waiting times are set by each network. See Networks.
Ethereum
32 ETH per validator
Up to 2,048 ETH per validator. The interface creates up to 20 validators in one Request. The API allows up to 150
Sui
1 SUI
To unstake part of a position, unstake at least 1 SUI and leave at least 1 SUI staked. Otherwise, unstake the whole position
Hedera
None
You stake the whole Account balance, not an amount
Tezos
None set by Ledger Enterprise
You delegate the whole Account balance, not an amount
Minimum balances
Some networks require an Account to keep a minimum balance. The network imposes these, not Ledger Enterprise. They are not fees and they are not spendable. The available balance deducts the base reserve only: 1 XRP or 1 XLM. The network also enforces the further amounts in the Detail column, but the available balance does not deduct them.
Ripple
1 XRP
The base reserve. The network locks a further 0.2 XRP for each object the Account owns. See the XRP Ledger reserves
Stellar
1 XLM
Two base reserves of 0.5 XLM. The network locks a further 0.5 XLM for each entry, so the minimum is (2 + entries) x 0.5 XLM. See the Stellar minimum balance
Every other network here
None
No balance has to stay in the Account
Each network can change its own figure by validator or protocol vote. The amounts above were checked against the network documentation on 7 October 2026.
One-time costs to create a destination
These are separate. They are paid once, when a destination is first used, and they are burned rather than paid to anybody.
Tron
About 1.1 TRX: 1 TRX, plus 0.1 TRX when the sending Account does not have enough bandwidth. See the Tron account documentation, checked on 7 October 2026
Sending to an address that does not yet exist on the network
Tezos
An allocation fee, added to the transaction fee
Sending to an unallocated, meaning empty or new, destination
Network-specific
Bitcoin
One transfer can draw on at most 100 UTXOs. The send form refuses a transfer that needs more, and gives the limit. See Bitcoin
Canton
One transfer can draw on at most 100 coin contracts
Canton
The reason attached to a transfer is up to 128 characters in the interface. The API does not enforce a limit
Related
Last updated