XLM is a “network lubricant,” and that choice dominates everything

Stellar is built to move and exchange assets on a fast, low-friction ledger. XLM is the ledger’s native currency, but it is not trying to be an “app token” with a revenue share story. Its first-order job is mechanical: pay network fees, satisfy minimum balance requirements, and support on-ledger liquidity routing when assets need a bridge.

The second job is underappreciated but real. Stellar’s path payments can cross the built-in exchange layer, so a sender can deliver one asset while the recipient receives another, provided there is a viable conversion path through order books and/or liquidity pools. The docs even show XLM explicitly inside conversion paths, which is how it becomes the “always-there” intermediary when two assets are otherwise illiquid against each other.

This design has a clean consequence for tokenomics. Demand for XLM is mostly “inventory demand” and “friction demand,” not staking demand. There is no protocol staking lockup that reliably eats float. If you want to model price behavior, you model float dynamics and liquidity, not emissions APR.

For a contrast case where staking and inflation are central, see our Polkadot tokenomics review.

Supply mechanics: pre-minted, inflation removed, and the 2019 burn that reset the cap

Stellar’s supply story is unusual in today’s market because it is mostly “done.” Stellar’s lumen supply metrics state that lumens are not mined and that all XLM that has ever existed and will ever exist was created when the network went live.

That statement needs one important historical footnote. For the first years, Stellar had a protocol inflation mechanism that increased lumen supply by 1% annually. Stellar’s docs quantify the total inflation-minted amount as 5,443,902,087.3472865 XLM and state inflation ended by validator vote on October 28, 2019.

Then came the structural reset. On November 4, 2019, SDF sent 55,442,095,285.7418 XLM to an account with no signers, permanently removing it from supply.

From a liquidity-structure perspective, this matters more than the headline “fixed supply.” It created a much tighter ceiling and clarified that remaining non-circulating supply would be a treasury distribution problem, not an emissions problem.

Current market trackers reflect that post-burn reality. As of March 7, 2026, total supply is listed as 50,001,786,883 XLM with 32,992,930,376 XLM circulating supply.

One nuance worth stating plainly: CoinGecko also shows “Max Supply = ∞.” That is an indexing choice, not a practical issuance schedule. Stellar’s own documentation and Learn materials assert no further lumens will be created post-inflation removal.

If you want a schedule-based issuance comparison, our Litecoin tokenomics review is a useful foil.

SDF treasury is the unlock schedule

XLM’s market float is largely a governance-and-treasury question because SDF started with a very large inventory and has an explicit mandate to deploy it into the ecosystem.

The most concrete “unlock” language is also from that 2019 plan. SDF said the Direct Development allocation was escrowed with a schedule to unlock 3B XLM per year for four years.

SDF also committed to a time horizon. It stated it intended to use or disperse most of its mandate lumens within ten years from the 2019 framework.

Here is the distribution framework as represented in SDF’s mandate accounting (original balances shown).

What matters for float is not the original buckets. It is the remaining inventory and the pace it becomes liquid. SDF’s mandate page reports a combined current balance of 16,925,943,372 XLM, last updated on March 6, 2026.

That remaining mandate inventory is the closest thing Stellar has to an “unlock schedule.” It is not time-locked by protocol. It is governed by policy, budgets, and market conditions, then executed by transfers.

Fees, reserves, and fiscal flows: XLM has sinks, but they are tiny

Stellar makes you hold XLM because the ledger is cheap to use and would otherwise be easy to spam. The protocol enforces both a minimum balance and transaction fees. Stellar’s docs define the base reserve as 0.5 XLM and state accounts must maintain a minimum balance of two base reserves, which is currently 1 XLM. Each subentry raises the minimum balance by another base reserve.

On the fee side, Stellar uses an inclusion fee model with a network minimum effective base fee of 100 stroops per operation. The docs define a stroop as 0.0000001 XLM, so the network-minimum fee works out to 0.00001 XLM per operation under fees and metering.

Fees are not a validator revenue stream. SDF’s developer-facing materials state fees do not go to validators or to SDF. Fees go into the protocol-level fee pool tracked in the ledger header.

Post-inflation removal, the fee pool is effectively a one-way sink. SDF’s inflation proposal explicitly said fees would still go to the fee pool and would be locked there, inaccessible and unused. Stellar’s docs also state no one has access to the fee pool, making it non-circulating, though validators could theoretically vote for a change that affects it.

In practical tokenomics terms, that sink is real but modest. Stellar’s base fees are designed to be tiny, and the docs note the fee pool grows very slowly.

There is a second XLM “holding cost” that is more meaningful at scale: reserves. Every trustline, offer, signer, and data entry pushes up minimum balances. That is a soft lock on some XLM, and it scales with usage. It is also reversible. Delete entries and XLM becomes spendable again.

Stellar’s newer smart contract layer introduces rent for smart contract ledger entries instead of base reserves, which changes how state occupancy is paid for. The docs frame this as rent for smart contract data and fees and metering for contract execution.

Liquidity provision is separate. Stellar’s protocol-native AMMs charge a 0.30% fee on trades, and SDF’s press release states that fee is distributed to liquidity providers. That is not an XLM sink. It is a redistribution inside the pool.

Governance: validator votes move parameters, not token holders

Stellar’s consensus is the Stellar Consensus Protocol (SCP), a Federated Byzantine Agreement construction. Nodes choose which other nodes they trust via quorum sets, and the network’s ability to reach agreement depends on those trust relationships. Token holdings are not the governance primitive.

Protocol changes follow an open proposal process defined in core and ecosystem standards, then activation is operational: validators decide which version of the protocol to run.

Final activation is operational. Validators decide which version of the protocol to run. That is not abstract. Stellar’s docs state the inflation mechanism was ended by validator vote on October 28, 2019.

That same governance surface controls several token-relevant parameters. Stellar’s docs state validators can vote to change the base reserve, and resource limits are determined by validator vote.

SDF still has practical influence. It authors major code, coordinates releases, and runs validators like many ecosystem organizations. But there is no on-chain, token-weighted “XLM governance” that lets passive holders vote supply or fees.

If you’re evaluating governance surfaces across protocols, our tokenomics methodology explains what we track.

Float reality: circulating supply is not the same thing as tradable supply

If you want to understand XLM market behavior, start with a basic split.

Circulating supply is the amount in public hands and considered tradeable by indexers. On March 7, 2026, CoinGecko reports 32,992,930,376 XLM circulating against 50,001,786,883 XLM total supply.

Non-float supply is everything that does not behave like free float, even if it exists on-chain. SDF’s remaining mandate inventory is the obvious piece. The mandate accounting reports 16,925,943,372 XLM still held across program wallets as of March 6, 2026.

The fee pool is another piece. Fees accrue into a protocol fee pool that is inaccessible, making it non-circulating unless a future protocol change alters it.

Then there is the soft-locked float created by minimum balances. Every account must maintain a minimum balance based on base reserves, and subentries add to that requirement. This is not vesting. It is operational collateral. It comes off the market when usage grows, and it comes back when users close entries.

Stellar also has liquidity pools, and they create a different form of float friction. Liquidity pool participation yields pool shares that represent ownership and cannot be transferred. The underlying assets, including XLM where applicable, remain withdrawable by LPs. So AMMs can reduce immediate spot liquidity, but they do not remove supply.

This is why I stay skeptical of FDV narratives for XLM. FDV is a clean number, but Stellar does not have a long tail of emissions or cliff unlocks scheduled by smart contracts. The real supply schedule is policy-driven treasury distribution plus a slow fee pool sink plus reversible reserve collateral.

Risk analysis: supply overhang is the dominant variable

Stellar’s token design is coherent for payments. Low fees, low minimum balance, and an always-available native asset make onboarding simpler and make path payments viable.

The strain comes from the same place it always comes from in pre-minted networks. A large treasury can be mission-aligned and still be a market overhang. SDF explicitly intends to deploy most of its mandate lumens within ten years, and it still reports 16,925,943,372 XLM held in mandate wallets as of March 6, 2026.

A similar “foundation inventory” lens comes up in our Hedera tokenomics review.

Top 3 risks

  1. Treasury distribution shock, Trigger: SDF accelerates spending, grants, investments, or distributions versus the market’s ability to absorb incremental liquid XLM. Mechanism: effective float rises, liquidity providers reprice inventory risk, and marginal demand clears at lower prices. Who bears it: spot holders first, then market makers and corridor operators when spreads widen. Measurable indicators: SDF mandate balances and wallet outflows, reported mandate totals (last updated March 6, 2026), and changes in circulating supply on major trackers.
  2. Parameter change risk (fees, reserves, and capacity), Trigger: validators vote to change base reserve, fee dynamics, or resource limits in response to spam, congestion, or evolving contract workloads. Mechanism: higher operational collateral (minimum balances) or higher effective fees reduce activity at the margin, which can thin on-ledger liquidity and weaken the “XLM as bridge” utility loop. Who bears it: high-frequency DEX users, wallets subsidizing users, and anchors that rely on predictable throughput. Measurable indicators: changes in stated network minimum fee (100 stroops), ledger capacity settings, and base reserve (0.5 XLM) in the docs and network tooling.
  3. Liquidity degradation in the routing layer, Trigger: order books and AMM pools lose depth in key corridors, or liquidity fragments across venues and assets. Mechanism: path payments fail more often or clear at worse rates, making the network less attractive for cross-asset settlement. That reduces organic reasons to hold XLM as inventory for routing. Who bears it: end users via slippage, anchors via worse execution, and issuers via reduced distribution. Measurable indicators: path payment success rates, AMM pool participation and swap activity, and observable spreads across major asset pairs.

Dominant risk: treasury distribution shock

This is the one that actually sets the range of outcomes.

Stellar removed the easy-to-model parts of dilution years ago. Inflation ended on October 28, 2019 by validator vote. SDF then burned 55,442,095,285.7418 XLM on November 4, 2019. Since then, the supply “schedule” is human. It is budget cycles, program decisions, and opportunistic deployments.

SDF is transparent in one important way. It publishes mandate wallets and balances, and it states an intent to use or disperse most of its lumens within ten years. That improves modelability versus foundations that publish nothing.

But there is still structural uncertainty for price and liquidity because “distribute” is not a single market behavior. A grant recipient might hold, might market sell, might use XLM as collateral, might route it into liquidity pools, might convert immediately to fiat to pay expenses. An investment might come with covenants, or it might not. A marketing distribution can behave like a drip, or like a campaign spike. None of those behaviors are enforceable by the protocol.

So the market ends up pricing the treasury as an embedded supply option. When risk appetite is high, traders discount it. When liquidity is thin, that same overhang dominates. This is why XLM can trade like a “mature” asset one month and like a high-beta treasury token the next, even when core protocol mechanics are unchanged.

The practical way to monitor it is boring. Track mandate balances and large on-chain movements from mandate-linked wallets. Track circulating supply changes. Watch exchange inflows. Those are the measurable precursors to float repricing. We publish ongoing crypto research that can support that monitoring.

If you are building on Stellar, this risk also has a second-order product implication. Thin XLM liquidity can raise the real cost of sponsoring users, market making on the SDEX layer, or operating corridor inventory, even if the protocol fee stays tiny. The base fee can be 100 stroops and the economic friction can still rise if XLM inventory risk rises.

For teams doing treasury policy work, distribution design, or reserve-and-fee impact assessments, this is where tokenomics design stops being theoretical and becomes liquidity engineering. If you ever need tokenomics consulting on a Stellar-native asset or on an XLM-funded program, the highest leverage work is usually modeling effective float and distribution pathways, not writing emission schedules.



This article is part of our Tokenomics Deep Dive series.