cryptosnif
EN ↗
EnglishFrançaisPortuguês (Brasil)EspañolLanguage keeps this subject. Country is selected separately on service pages.
Crash test / Smart contract platform / CT-XLM-001

Stellar (XLM)

stellar-mainnet · Native asset · Documentation reviewed
The verdict

Unrated · 0% Evidence coverage

Operational strength remains unproven; unrated with 0% scoring coverage.

Documentary mechanisms alone cannot establish actual network behavior or investment outcomes.

Inspect the evidence
UnratedOverall score / 100
0%Evidence coverage
13 checks pending85% coverage and 3 essential checks required for a score
2026-10-05Documentation checked · Candidate method 0.1.0

Documentation review · Reviewed · catalogue-documentary-1

The source review explains documented mechanisms. Independent network checks remain pending.

Promise

Stellar Core's documented purpose is to maintain a ledger and process transactions in agreement with peers. This dossier examines that software description for native XLM and identifies the evidence needed to assess how the deployed network reaches agreement and behaves during failures.

Established facts

The source identifies the implemented agreement mechanism as the Stellar Consensus Protocol, which it calls federated consensus. A replicated state machine means participating computers maintain copies of a ledger and process transactions using agreed state-transition rules. Stellar Core keeps a local copy of a cryptographic ledger and processes transactions in consensus with a set of peers. The implementation is described as C++20 software with support for Linux, macOS, and Windows operating systems. These descriptions do not establish which peers current operators trust, whether those peers are independent, or how the deployed network behaves during failures. Current quorum configuration, protocol amendments, control, usage, token supply, ownership, liquidity, throughput, and a complete incident history remain unverified by this documentary lot.

Unknowns

The separate protocol explanation and architecture overview linked by the README were not examined here. The source identifies federated consensus, but the current peers trusted by operators and the deployed quorum configuration remain unverified.

Current operator independence, protocol amendments, throughput and behavior during failures also lack dated observations. Supply, holder ownership, actual use, liquidity and the complete incident record remain outside the evidence gathered.

Consequences

The replicated-state description identifies the agreement process as a central subject for further research. To assess resilience, you would need the deployed peer and quorum configuration and reproducible observations of behavior under stated failure conditions.

The supported operating systems listed in the README describe software compatibility. This dossier contains no runtime test of that compatibility. Neither the software description nor the operating-system list establishes present network performance or an investment outcome.

Verdict

Unrated, with 0% coverage of the scoring criteria. Stellar Core's ledger and agreement role are documented. The evidence reviewed here leaves the network's present operational strength unresolved, and the coverage percentage records the absence of admitted scoring observations.

Evidence that would change it

Reviewing the pinned protocol explanation would deepen the mechanism description. Dated identity checks, actual quorum configurations and independently reproduced network observations would then address operation and control. Verified economic and incident evidence would be needed alongside calibration and editorial review before a rating.

02 / Crash test

Each check earns its result.

Candidate method 0.1.0. Unknown results are excluded from the score calculation.
CheckWeightResult
Exact asset identityEssential3%Verification pending
Observable use15%Verification pending
Economic role of the token10%Verification pending
Supply mechanismsEssential10%Verification pending
Ownership concentration8%Verification pending
Value capture7%Verification pending
Control powersEssential10%Verification pending
Security verification7%Verification pending
Decision process8%Verification pending
Accountability7%Verification pending
Incident history6%Verification pending
Operational continuity4%Verification pending
Execution conditions5%Verification pending

Family-specific checks: Validator independence, upgrades, execution and fees.

03 / Evidence

Inspect the evidence

Sources behind this analysis

Stellar: pinned stellar/stellar-core overview (88d2431d7245)

The pinned Stellar Core README describes its software as a replicated state machine. That term means participating computers maintain copies of a ledger and process transactions using agreed state-transition rules. Stellar Core keeps a local copy of a cryptographic ledger and processes transactions in consensus with a set of peers. It identifies the implemented agreement mechanism as the Stellar Consensus Protocol and calls it federated consensus. The source links a separate protocol explanation and a code-architecture overview; those linked documents were not examined in this dossier. Its implementation is described as C++20 software with Linux, macOS and Windows support. A supported operating system is a software claim, without a runtime test here. These descriptions do not establish which peers current operators trust, whether those peers are independent, or how the deployed network behaves during failures. The documentary subject is native XLM on Stellar. Current quorum configuration, protocol amendments, control, usage, token supply, ownership, liquidity, throughput and a complete incident history remain unverified.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 7bda10d9a56f310bff4bd54088d38f54ba1f7526fa435dd43a37dc6cda523073

Only original summaries are distributed. Licensed raw market data stays private.

Continue the investigation