> 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, and governance objects on Ledger Enterprise.

## Names and text

<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, no special characters</td></tr><tr><td>Policy name</td><td>45 characters, unique in the Workspace</td></tr><tr><td>Whitelist name</td><td>45 characters</td></tr><tr><td>Whitelist entry label</td><td>50 characters</td></tr><tr><td>Portfolio name</td><td>120 characters, unique in the Workspace</td></tr><tr><td>Note on any Request</td><td>1,000 characters in the interface. The API does not enforce a limit</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 four send Rules are checked in order. The first Rule whose amount threshold matches is the one that applies.

> **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's quorum cannot be higher than the number of **distinct people** it names. Somebody who belongs to several groups in the same step counts once.

## 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>Both parts of a split position must keep more than 1 SUI</td></tr><tr><td>Hedera</td><td>None</td><td>You stake 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, they are not spendable, and they reduce the available balance.

<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. A further 0.2 XRP for each object the Account owns</td></tr><tr><td>Stellar</td><td><strong>1 XLM</strong></td><td>Two base reserves of 0.5 XLM. A further 0.5 XLM for each entry</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 on 11 September 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</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 use at most <strong>100 UTXOs</strong> at time of Request creation. Pre-broadcast limit is higher.</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></td></tr></tbody></table>

## Related

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