How Stellar’s Minimum Balance Shapes a New Account

A new Stellar account must receive enough XLM to meet its minimum balance before it can exist on the ledger. That balance is a reserve: it remains in the account, but the account cannot spend below the required floor. The amount depends on the network’s base reserve and the ledger entries attached to the account, so funding only the account’s initial requirement can leave no spendable XLM for later actions.

Plan the first deposit around the account’s intended use. A wallet that will hold only XLM needs less reserved than one that will add trustlines, offers, or extra signers. If an application funds accounts for users, it can also sponsor reserves, shifting who must hold the XLM. A separate route problem can arise when funds pass through a swap or intermediary; Biswap’s guide to routes behind stuck transfers explains why tracing a transfer path matters before retrying it.

How much XLM does a new Stellar account need?

A new, self-funded Stellar account needs two base reserves to be created. A base reserve is the unit the network uses to calculate the minimum balance; the network’s current parameter determines its XLM value. Validators can change that parameter, so check the current value on the network you are using rather than relying on a remembered amount.

The account’s minimum balance rises as it gains subentries. A trustline for a traditional asset, an offer, an additional signer, and a data entry each add a reserve requirement. A pool-share trustline counts as two subentries. These entries occupy ledger space, and the reserve makes the account retain enough XLM while those entries remain.

That makes “fund the account with the minimum” an incomplete instruction. Estimate the reserve for the account after its initial setup, then leave additional XLM above that floor for fees and any planned activity. The reserve is not a transaction fee: fees are charged separately, and the account’s available balance can also be reduced by selling liabilities from open offers.

How do you create and fund the account?

Use Stellar’s CreateAccount operation to establish a new account from an existing funded account. The source account pays the transaction fee and supplies the destination’s starting balance. A public key by itself does not create a ledger account; the operation must be included in a valid transaction and reach the network.

Before submitting, calculate the required starting balance from the current base reserve and the entries the account will need. The destination must receive enough to satisfy its initial minimum. If it will immediately add trustlines or other subentries, budget those reserves too. For a non-XLM asset, the destination needs a trustline before it can receive that asset; an XLM payment alone does not create one.

On test networks, a network-provided Friendbot can create and fund accounts. Applications can discover the relevant endpoint through the network’s information rather than hard-coding an address. Test-network XLM has no mainnet value, and a testnet funding flow does not supply XLM on the public network. On mainnet, the source account must already hold real XLM or an existing account or service must sponsor the setup.

• Confirm that the source is funded and can pay the transaction fee.
• Check the destination public key and the network passphrase used to build the transaction.
• Include reserves for the account itself and any planned trustlines, offers, signers, or data entries.
• For a non-XLM deposit, establish the required trustline before sending the asset.

Can another account cover the minimum balance?

Yes. Stellar’s sponsored-reserves mechanism lets one account carry reserve requirements that would otherwise sit on another account. A sponsor can cover the new account’s initial reserves, allowing it to be created with a starting balance of zero, and can sponsor later entries such as trustlines. The sponsored account still needs XLM for transaction fees unless those fees are separately covered.

Sponsorship is explicit. The transaction brackets the sponsored operation with BeginSponsoringFutureReserves and EndSponsoringFutureReserves, and the relevant accounts must sign. The sponsor’s reserve burden grows while the sponsored entries exist. Removing a sponsored entry releases that reserve back to the sponsor, rather than turning it into spendable balance for the user.

This is useful for wallets and services that want to onboard users without first requiring them to acquire XLM. It also moves an operational responsibility to the sponsor: it must keep enough XLM available for the reserves it accepts. Sponsorship is therefore a funding design, not a waiver of the network’s storage requirement.

Why can a funded account still fail to send?

An account can have a positive XLM balance and still lack enough available balance to complete an operation. The network enforces the minimum balance after changes, while open sell offers reduce the amount available above that minimum. A transaction that adds a trustline can fail if the account has no room for the added reserve, even when it can pay the transaction fee.

When a setup or transfer fails, inspect the operation result and current account state before sending again. Check whether the account exists, whether the asset trustline is present, whether an offer or signer has raised the reserve, and whether liabilities constrain the spendable amount. If a transfer crossed a swap or routing service, verify its status at each step instead of treating a pending or failed route as proof that the destination needs another deposit.

For most self-custody users, the simplest approach is to create the account with enough XLM for its planned ledger entries and a modest fee buffer, then add only the trustlines and entries they need. For hosted onboarding, sponsored reserves can remove the initial XLM hurdle, provided the sponsor accounts for the reserve commitment and keeps transaction fees covered separately.