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

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

<table><thead><tr><th width="204.390625">Field</th><th>Limit</th></tr></thead><tbody><tr><td>Account name</td><td>45 characters, unique in the Workspace</td></tr><tr><td>Policy name</td><td>45 characters, unique in the Workspace</td></tr><tr><td>Whitelist name</td><td>45 characters, unique in the Workspace</td></tr><tr><td>Whitelist entry label</td><td>50 characters</td></tr><tr><td>Whitelist entry address</td><td>200 characters</td></tr><tr><td>Group name</td><td>45 characters, unique in the Workspace</td></tr><tr><td>User name</td><td>19 characters in the interface, 45 in the API. Unique among active users and pending registrations</td></tr><tr><td>Portfolio name</td><td>45 characters in the interface, 120 in the API. Unique among active Portfolios, with no difference between upper and lower case</td></tr><tr><td>Note</td><td>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</td></tr></tbody></table>

## Rules per Account

Rules are set per operation type. Which ones you can add depends on the asset.

<table><thead><tr><th width="119.0546875">Operation</th><th width="146.6484375">Available on</th><th width="118.46875">Required</th><th width="85.71875">Max Rules</th><th width="118.125">Amount thresholds</th><th width="118.29296875">Whitelists</th></tr></thead><tbody><tr><td>Send</td><td>All assets</td><td>Yes</td><td>4</td><td>Yes</td><td>Yes</td></tr><tr><td>Receive</td><td>Canton only</td><td>Yes, on Canton</td><td>1</td><td>No</td><td>No</td></tr><tr><td>Stake</td><td>Assets that support staking</td><td>No</td><td>1</td><td>No</td><td>No</td></tr><tr><td>Sign message</td><td>Assets that support it</td><td>No</td><td>1</td><td>No</td><td>No</td></tr><tr><td>Contract interaction</td><td>EVM networks</td><td>No</td><td>1</td><td>Yes</td><td>Yes</td></tr><tr><td>Contract deployment</td><td>EVM networks</td><td>No</td><td>1</td><td>Yes</td><td>No</td></tr><tr><td>Token activation</td><td>No supported asset today</td><td>No</td><td>1</td><td>No</td><td>No</td></tr></tbody></table>

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**](/help-center-v2/guides/accounts/creating-and-editing-accounts.md#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**](/help-center-v2/reference/networks/canton.md).

## Approval steps

A step names **one group or a list of Operators**, never both.

| Where     | Quorum of a step                                                                               |
| --------- | ---------------------------------------------------------------------------------------------- |
| 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**](/help-center-v2/reference/networks.md).

<table><thead><tr><th width="119.6015625">Network</th><th width="160.87890625">Minimum</th><th>Notes</th></tr></thead><tbody><tr><td>Ethereum</td><td>32 ETH per validator</td><td>Up to 2,048 ETH per validator. The interface creates up to 20 validators in one Request. The API allows up to 150</td></tr><tr><td>Sui</td><td>1 SUI</td><td>To unstake part of a position, unstake at least 1 SUI and leave at least 1 SUI staked. Otherwise, unstake the whole position</td></tr><tr><td>Hedera</td><td>None</td><td>You stake the whole Account balance, not an amount</td></tr><tr><td>Tezos</td><td>None set by Ledger Enterprise</td><td>You delegate the whole Account balance, not an amount</td></tr></tbody></table>

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

<table><thead><tr><th width="223.0078125">Network</th><th width="152.98046875">Minimum to keep</th><th>Detail</th></tr></thead><tbody><tr><td>Ripple</td><td><strong>1 XRP</strong></td><td>The base reserve. The network locks a further 0.2 XRP for each object the Account owns. See the <a href="https://xrpl.org/docs/concepts/accounts/reserves">XRP Ledger reserves</a></td></tr><tr><td>Stellar</td><td><strong>1 XLM</strong></td><td>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 <a href="https://developers.stellar.org/docs/learn/fundamentals/lumens">Stellar minimum balance</a></td></tr><tr><td>Every other network here</td><td>None</td><td>No balance has to stay in the Account</td></tr></tbody></table>

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.

<table><thead><tr><th width="130.0546875">Network</th><th width="289.60546875">Cost</th><th>When it applies</th></tr></thead><tbody><tr><td>Tron</td><td>About 1.1 TRX: 1 TRX, plus 0.1 TRX when the sending Account does not have enough bandwidth. See the <a href="https://developers.tron.network/docs/account">Tron account documentation</a>, checked on 7 October 2026</td><td>Sending to an address that does not yet exist on the network</td></tr><tr><td>Tezos</td><td>An allocation fee, added to the transaction fee</td><td>Sending to an unallocated, meaning empty or new, destination</td></tr><tr><td>Hedera</td><td>None, but an Account must be activated before first use</td><td>See <a href="/help-center-v2/reference/networks/hedera.md"><strong>Hedera</strong></a></td></tr></tbody></table>

## Network-specific

<table><thead><tr><th width="139.7109375">Network</th><th>Limit</th></tr></thead><tbody><tr><td>Bitcoin</td><td>One transfer can draw on at most <strong>100 UTXOs</strong>. The send form refuses a transfer that needs more, and gives the limit. See <a href="/help-center-v2/reference/networks/bitcoin.md#the-100-output-limit"><strong>Bitcoin</strong></a></td></tr><tr><td>Canton</td><td>One transfer can draw on at most <strong>100</strong> coin contracts</td></tr><tr><td>Canton</td><td>The reason attached to a transfer is up to <strong>128 characters</strong> in the interface. The API does not enforce a limit</td></tr></tbody></table>

## Related

* [**Creating and editing Accounts**](/help-center-v2/guides/accounts/creating-and-editing-accounts.md)
* [**Policies**](/help-center-v2/administration/governance/policies.md)
* [**Whitelists**](/help-center-v2/administration/governance/whitelists.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/limits.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.