Methodology
XRPline surfaces trust lines, reserve estimates, and freeze-related heuristics from public ledger data. We do not sell rankings, custody funds, or ask for seed phrases — and this page is the source of truth for how measurements work.
Key facts
- Publisher: XRPline
- Updated: 20 October 2026
What we measure
- Manager — currency, issuer, balance, limit, and flag fields from public line tables
- Cleaner — lines with ≈0 balance and an estimate of freeable incremental owner reserve
- Risk — heuristic labels (for example freeze indicators) to prioritize human review — not financial advice
Data sources
Where applicable we use public XRPL JSON-RPC methods (for example account_lines, account_info, server_state) and XRPSCAN API/explorer-grade metadata for issuer context. Base and incremental reserve must be read from live network state — fee voting and amendments can change the numbers users remember from blogs.
Updated 20 October 2026. If a UI figure disagrees with your wallet or explorer, treat the ledger as authoritative.
What we never do
- We never ask for seed phrases or private keys
- We never custody XRP or IOUs
- We never sell paid placement inside Manager/Cleaner/Risk views
- We never claim Risk labels are audited safety scores or investment recommendations
How Risk labels are produced
Risk heuristics highlight conditions that commonly block or surprise users (freeze flags, empty-line reserve drag, suspicious ticker/issuer mismatches when detectable). Labels exist to order attention. They are not a purchasable ranking ladder and are not sold as SEO “TOP” placements.
Educational comparison pages and guides may use tables; product Risk is separate from editorial lists. Transparency here is intentional E-E-A-T: methodology pages that confess fake rankings get sites punished — we refuse that pattern.
Freshness
Documentation carries visible update dates. Protocol constants (reserves, flags) are cross-checked against live server_state when the app loads network strips. If an amendment changes reserve math, product UI should reflect live reads even when a guide still shows a “commonly cited” approximate figure.
Publisher
Published by XRPline · Updated 20 October 2026.
Why this page matters for E-E-A-T
Search engines and AI citation systems reward clear publisher identity, dated updates, and transparent methods. On methodology/ XRPline states who publishes (the organization), what we measure, and what we refuse: custody, seed requests, and paid Risk placement.
We keep About, Methodology, Security, Privacy, and Disclaimer readable without contradictory disclaimers buried in tiny type. Harmful self-sabotage copy (“our rankings are fake / paid”) is never used — Methodology instead says Risk is heuristic and not for sale.
Experience is shown through working Manager/Cleaner/Risk flows and dated docs, not through invented personal brands. Expertise is protocol-accurate copy about TrustSet, RippleState, OwnerCount, and freeze flags. Authority comes from consistent Organization publisher markup and public methodology. Trust comes from non-custodial signing and explicit independence from Ripple Labs.
Trust lines in one paragraph of facts
A trust line is a RippleState object established by TrustSet so an XRPL account can hold a specific issued currency from a specific issuer up to LimitAmount.value. Native XRP does not use trust lines. Missing receiver lines commonly fail inbound IOU payments with tecNO_LINE. Empty lines still raise OwnerCount and typically lock incremental owner reserve (often cited near ~0.2 XRP after late-2024 reductions — confirm live server_state).
XRPline Manager lists lines; Cleaner highlights ≈0-balance reclaim candidates; you Sign TrustSet in your wallet for every create/change/clear. Cross-check issuers with explorers and issuer guides.
When budgeting XRP, remember reserve is locked collateral for owned objects, not a fee burned on each TrustSet. Closing an empty line after balance is zero and the limit is cleared is how incremental reserve returns to spendable balance.
Internal map of the documentation cluster
Guides teach workflows (set, remove, reserves). Problems decode failures (tecNO_LINE, cannot remove). Glossary defines entities (TrustSet, freeze, OwnerCount). Intents mirror search jobs (intents hub). FAQ answers extractable questions. Tools deep-link into the app.
Each landing keeps BLUF in the first sentences, then expands into steps, edge cases, and FAQ blocks with FAQPage JSON-LD where Q&A exists. BreadcrumbList and Article schema identify the page; Organization is the author — never a fabricated person.
Legitimate GEO practices we use (and refuse)
We use BLUF openings, concrete numbers, FAQPage schema, hreflang locales, robots Allow for major search and AI crawlers, sitemap.xml, and llms.txt. We refuse PBN spam, automated forum injection for Harmonic Centrality gaming, and fabricated author farms. Useful structured data and honest methodology beat short-lived manipulation.
Common Crawl and other open crawls index public pages; the durable strategy is crawlable, factual, interlinked documentation — not disposable spam nodes. Freshness comes from visible update dates and live reserve reads in product UI, not from rewriting the same thin page daily.
FAQ
Can I buy a better Risk score?
No. Methodology forbids paid placement in product views. Risk labels are heuristics for review priority, not for-sale rankings.
Where do reserve numbers come from?
From validated ledger server_state (and equivalent fields). Always confirm live values before budgeting XRP for new trust lines.