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

# Stellar (XLM)

Stellar (XLM) on Ledger Enterprise: memos, the four memo types, and when you must include one.

## How Stellar differs

Stellar uses a **minimum balance** model. An Account cannot hold a zero balance. The network locks a multiple of the base reserve in every Account, and locks one more multiple for each entry the Account holds.

The locked amount is not a fee and it is not spendable. It reduces the available balance for as long as the Account exists.

Payments also carry an optional **memo**, which identifies the payee inside an address that many customers share.

For the protocol itself, see the [Stellar developer documentation](https://developers.stellar.org/).

## Token coverage

Ledger Enterprise supports **XLM only** on Stellar. Issued assets and trust lines are not supported.

## Minimum balance

The network sets the base reserve, not Ledger Enterprise. It can change by protocol vote.

The minimum balance is `(2 + number of entries) x base reserve`, where the base reserve is **0.5 XLM**. A plain Account therefore locks **1 XLM**.

> **Note:** The base reserve was checked against developers.stellar.org on 16 September 2026. It can change by protocol vote.

Because assets and trust lines are not supported here, an Account normally holds no entries beyond the minimum.

## Memos

A memo carries extra information with a Stellar payment. Exchanges and custodians use it to identify **who** a payment is for, inside an address that many customers share.

The memo is optional in the transaction form. Choose a **memo type** first, then enter the value.

<table><thead><tr><th width="117.16796875">Type</th><th>What it holds</th></tr></thead><tbody><tr><td><strong>Text</strong></td><td>Up to 28 bytes of text</td></tr><tr><td><strong>ID</strong></td><td>A whole number. The form checks the upper limit</td></tr><tr><td><strong>Hash</strong></td><td>A transaction ID</td></tr><tr><td><strong>Return</strong></td><td>A transaction ID, used to return a payment to its sender</td></tr></tbody></table>

**Text** and **ID** are the ones recipients normally ask for. Use the type your recipient specifies, not the one that looks closest.

> **Warning:** If your recipient asks for a memo, you must include it, with the right type. A payment that arrives without the memo reaches the right address but cannot be matched to your Account. Recovering it means contacting the recipient's support team.

Take the memo and its type from the recipient at the same time as the address.

> **Note:** 28 bytes is not the same as 28 characters. Accented and non-Latin characters use more than one byte each. If a text memo is rejected as too long, this is usually why.

## Related

* [**Sending assets**](/help-center-v2/guides/transactions/sending-assets.md)
* [**Networks**](/help-center-v2/reference/networks.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/networks/stellar.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.
