What the evidence supports today
XLM has protocol-required uses with reproducible supply definitions
SupportedStellar documentation requires XLM for transaction fees and account or ledger reserves and publishes a method and API fields for original, burned, fee-pool, foundation-held, total, and circulating lumen supply.
Layer North view: These are direct protocol uses and unusually explicit supply definitions, but they do not create a redemption claim or guarantee market value.
X02X04Safety and liveness depend on configured quorum relationships
SupportedUnder the Stellar Consensus Protocol, each validator chooses trusted nodes and a threshold in its quorum set; blocking sets can prevent agreement, and unsafe quorum topology can threaten network safety.
Layer North view: Permission to run a validator does not by itself demonstrate diverse effective control. The network depends on how operators configure trust and on the organizations occupying central quorum positions.
X03X05Current effective validator independence is not reproduced
UnresolvedThis draft has not independently mapped live validator organizations, quorum-set overlap, minimal blocking sets, shared infrastructure, software versions, or the influence of Stellar Development Foundation-operated nodes.
Layer North view: Node count alone would not resolve entity concentration or correlated failure in a federated trust graph.
X03X05X06Snapshot, not a live ticker
Each value is tied to a named source and observation date. Market rank is context—not a quality score.
CoinGecko API cohort snapshot; rank is not a protocol-quality or liquidity measure.
As of 2026-08-13 X01The Stellar supply guide reported 50,001,786,839.9124767 XLM at its 21 July 2026 API snapshot, including the non-circulating fee pool.
As of 2026-07-21 X02Documented minimum for a classic operation outside surge pricing; resource fees and network conditions can change actual cost.
As of 2026-08-13 X04Two base reserves at the currently documented 0.5-XLM base reserve; subentries and ledger entries add requirements.
As of 2026-08-13 X02Fees and reserves create use; the protocol no longer inflates supply
XLM pays fees and supports ledger-state requirements
SupportedStellar requires XLM for inclusion and resource fees, and account balances must cover base reserves that rise with relevant subentries and ledger entries.
Layer North view: This deters spam and prices ledger use, but low unit fees do not by themselves establish aggregate token demand or investment value.
X02X04Inflation ended and a large supply reduction was executed
SupportedStellar documentation says the original network created 100 billion XLM, the former one-percent inflation mechanism ended by validator vote in 2019, and burned lumens reduced current total supply to about 50 billion.
Layer North view: No protocol mining issuance remains, while distribution from foundation-administered accounts can still change circulating supply.
X02X07Foundation-administered balances remain material
QualifiedThe supply methodology separately identifies the Stellar Development Foundation mandate balances and circulating supply, and the Foundation publishes the rationale for its 2019 burn and remaining allocations.
Layer North view: Transparent addresses aid monitoring, but future distributions, grants, sales, and counterparties still affect float and concentration.
X02X07Validators choose trust rather than compete for stake or hashpower
Quorum sets are operator-configured
SupportedEach Stellar Core validator selects other validators and thresholds it trusts; combinations satisfying those thresholds form quorum slices used in federated voting.
Layer North view: The model avoids protocol mining and staking, but transfers critical risk to quorum configuration, identity judgments, and topology monitoring.
X03X05Blocking and safety are topology-dependent
SupportedThe protocol guide explains that a blocking set can stop a node from reaching agreement and that safety is prioritized, so ledgers can stall while nodes wait for agreement.
Layer North view: Operational diversity and quorum intersection must be empirically measured; marketing descriptions of decentralization are insufficient.
X03Validator software and protocol versions require coordination
SupportedStellar publishes validator administration guidance and signed Stellar Core releases, including protocol-support and security-related changes.
Layer North view: Open releases make changes inspectable, but production version adoption and time-to-patch are not established by the repository alone.
X05X06Open software does not settle deployment or liquidity questions
The core implementation has an active public release record
ObservedThe Stellar Core repository publishes tagged releases and release notes covering consensus, networking, performance, and security-protocol work.
Layer North view: Repository activity is useful evidence, but this draft lacks an independent production-node inventory and complete vulnerability or outage ledger.
X06Market rank is only a provider snapshot
ObservedCoinGecko placed XLM at rank #20 in the selected API cohort and reported markets across third-party venues.
Layer North view: The snapshot does not measure spread, executable depth, derivatives leverage, custodian concentration, or withdrawal resilience.
X01Material risks and reassessment triggers
Impact labels are editorial judgments, not forecasts of price direction. Unsupported likelihood estimates remain unrated.
Quorum-set concentration and correlated failure
SupportedSCP safety and liveness depend on operator-selected trust relationships, while the effective live topology and common infrastructure have not been independently mapped.
Reassess when: A reproducible live quorum graph identifies entities, minimal blocking sets, quorum intersection, hosting overlap, and change through incidents.
X03X05Client and upgrade coordination
SupportedValidators must deploy compatible, secure Stellar Core versions and coordinate protocol upgrades without creating correlated defects or extended liveness loss.
Reassess when: Version adoption, security advisories, patch latency, upgrade votes, and outage recovery are independently tracked.
X05X06Foundation balance and distribution concentration
QualifiedSDF-administered balances are transparently categorized but remain material to circulating-supply growth and ecosystem funding.
Reassess when: Current mandate accounts, distributions, counterparties, restrictions, and entity-adjusted ownership are independently reconciled.
X02X07Executable market liquidity and custody
UnresolvedA high provider rank does not establish executable depth, clean price formation, custodian solvency, or market resilience under stress.
Reassess when: Cross-venue spread, depth, slippage, market-maker, derivatives, custody, and withdrawal tests are completed.
X01Is XLM a good investment? Evidence to test, not a recommendation.
The report does not issue a price target. It shows the observations that support the case, the countercase, and the signals that could change either.
- XLM has direct protocol utility for fees, account reserves, and ledger resources.
- Supply categories and calculation methods are publicly documented, including burns and foundation balances.
- Stellar Core, consensus documentation, and validator configuration guidance are open for inspection.
- Federated consensus depends on a trust graph whose current entity-level concentration is not reproduced.
- Foundation-administered balances remain a material distribution factor even without protocol inflation.
- Open source and market rank do not establish secure deployment or executable liquidity.
- Rebuild the live quorum graph, validator entities, blocking sets, and infrastructure overlap.
- Track Stellar Core versions, security releases, protocol upgrades, outages, and recovery times.
- Reconcile supply categories, SDF mandate distributions, ownership, and venue liquidity.
Claim-to-source record
Primary records establish documented rules and project-reported status. Dated measurements add observable context; neither substitutes for independent market, legal, or counterparty evidence.
Limitations, disclosures and change log
Known limitations
- Vinoth Kanna is the named analyst, but analyst sign-off has not been recorded for this draft. Jack General is the named reviewer; reviewer approval and independence have not been confirmed.
- No live validator, quorum-set, blocking-set, hosting, or software-version dataset was independently reproduced.
- The supply API figures were not recalculated from raw ledger data in this draft.
- This is not a complete protocol-upgrade, vulnerability, outage, or ecosystem incident history.
- Beneficial ownership, custodian exposure, derivatives leverage, and standardized market depth remain unmeasured.
- Market rank is a dated CoinGecko snapshot, not a durable fact or quality score.
Report disclosure
- Sponsorship
- No project sponsorship has been disclosed for this draft as of 13 August 2026. This statement has not received final publication sign-off.
- Affiliate links
- No affiliate links appear in this report.
- Holdings
- As of 13 August 2026, Vinoth Kanna and Jack General disclosed no crypto holdings or other material conflicts. These are personal disclosures, not independently verified statements.
- Automation
- Automation assisted source collection and drafting; named human verification and sign-off are pending.
Created an internal noindexed Stellar evidence draft separating XLM protocol utility and supply accounting from quorum-topology, deployment, treasury-distribution, and liquidity gaps.