Data Sources and Analysis Infrastructure

The XRP Ledger is a public blockchain, meaning all transaction data is permanently recorded and freely accessible. This transparency is a major advantage for fundamental analysis.

Primary XRPL Explorers:

XRPScan (xrpscan.com)

XRPScan is the most comprehensive XRPL explorer, offering detailed transaction history, account analytics, and network statistics. Key features include rich list tracking (showing largest XRP holders), validator information, amendment status, and DEX activity monitoring. For valuation purposes, XRPScan provides essential data on active addresses, transaction volumes, and fee burns.

Bithomp (bithomp.com)

Bithomp offers a user-friendly interface particularly useful for account-level analysis. It provides transaction history, balance tracking, and NFT information. The interface is cleaner than some alternatives, making it useful for quick lookups and verification.

XRPL Explorer (livenet.xrpl.org)

This is Ripple's official explorer, providing authoritative network statistics including ledger information, amendment tracking, and validator data. While less feature-rich for account analysis, it's the definitive source for network health metrics.

Key On-Chain Metrics to Track:

Transaction metrics form the core of utility analysis. Track daily transaction count (typically 1-2 million), transaction types breakdown (payments vs. DEX vs. account operations), and fee burns (XRP permanently destroyed). These indicate actual network usage.

Account metrics reveal adoption trends. Monitor total accounts (currently ~5 million), daily/weekly/monthly active accounts, new account creation rate, and the distribution of holdings across accounts.

DEX metrics matter for XRPL ecosystem health. Track trading volume by pair, liquidity depth, bid-ask spreads, and AMM pool sizes if relevant.

Network health indicators include ledger close times (should be ~4 seconds), validator participation rates, and any UNL (Unique Node List) changes.

API Access:

The XRPL provides free, open API access via WebSocket connections. No API key is required. The official documentation at xrpl.org/docs provides comprehensive guidance on querying ledger data, account information, and transaction history.

Common queries include account_info (balance and settings), account_tx (transaction history), ledger (ledger data), and server_info (node status). These can be executed programmatically for automated data collection.

Third-Party APIs:

Bitquery offers a GraphQL interface for XRPL data with historical analysis capabilities. While free tiers exist, heavy usage requires paid plans. The advantage is cross-chain analysis capability.

Various community-built APIs exist but vary in reliability and maintenance status. Always verify data from community sources against official explorers.

Not all data sources are equally reliable. Establish a hierarchy:

Tier 1 - Most Reliable: Direct ledger queries return cryptographically verified data. If you query the ledger directly and multiple validators confirm, the data is as reliable as blockchain technology allows.

Tier 2 - Generally Reliable: Major explorer aggregations from XRPScan or Bithomp involve some processing but use known methodologies and have track records of accuracy.

Tier 3 - Use with Caution: Single-source claims, unverified aggregations, and self-reported metrics should be verified before use in models.

---

Primary Sources:

CoinGecko aggregates pricing from multiple exchanges, providing volume-weighted average prices. It offers market cap calculations, volume by exchange, and free API access. CoinGecko attempts to filter wash trading, though imperfectly.

CoinMarketCap provides similar data with different methodology. It has wider retail recognition and is often the reference for mainstream media. Some differences from CoinGecko exist due to methodology choices.

TradingView offers charting capabilities with technical indicators. It provides exchange-specific data and is useful for price pattern analysis, though less useful for fundamental valuation.

Exchange Direct APIs from Binance, Coinbase, Kraken, etc. provide the most accurate data for that specific venue. For institutional analysis, direct exchange data may be preferred.

Key Market Metrics:

Price data should include spot prices from multiple exchanges, 24-hour high/low, historical OHLCV (open/high/low/close/volume), and volume-weighted average price (VWAP).

Volume data requires skepticism. Reported exchange volume often includes wash trading. Use "real volume" estimates where available, and cross-reference multiple sources.

Market structure metrics include order book depth, bid-ask spreads, and large trade tracking. These indicate market liquidity and potential price impact of trades.

XRP derivatives provide additional market intelligence:

Coinglass (coinglass.com) tracks funding rates (indicating directional bias), open interest (total position size), liquidation data, and long/short ratios across major exchanges.

Positive funding rates indicate bullish positioning (longs paying shorts). Negative funding indicates bearish positioning. Large open interest increases suggest conviction; decreases suggest position closing.

Santiment offers social metrics (social volume, sentiment), development activity tracking, whale transaction monitoring, and custom dashboards. Useful for sentiment analysis alongside fundamental data.

Messari provides institutional-grade research reports, standardized metrics across assets, and detailed asset profiles. Requires subscription for full access but provides professional-quality analysis.

CoinMetrics focuses on network data with institutional methodology, offering both free and paid tiers. Known for rigorous data standards.

---

Quarterly XRP Markets Reports:

Ripple publishes quarterly reports at ripple.com/insights approximately one month after each quarter ends. These reports contain critical information including XRP sales by Ripple, escrow release and return data, ODL volume updates, and market commentary.

These reports are the primary source for ODL volume data, which is not directly observable on-chain. However, remember this is self-reported data without independent verification.

Other Ripple Disclosures:

Blog posts announce partnerships, product updates, and regulatory commentary. SEC filings (related to the lawsuit) contain financial disclosures and legal positions. Leadership communications on social media and at conferences provide strategic direction signals.

The Ripple escrow is trackable on-chain, providing verifiable data:

Monthly releases unlock up to 1 billion XRP on the first of each month. The actual release is often less than the maximum. Unused XRP returns to escrow with new unlock dates.

Track: monthly release amounts, return to escrow amounts, net circulation change, and remaining escrow balance (currently ~40 billion XRP).

The formula: Net Monthly Change = Released - Returned - Burned

ODL (On-Demand Liquidity) volume is the key utility metric but is challenging to verify:

Ripple's quarterly reports provide self-reported figures (currently ~$2B quarterly, ~$8B annually). Independent verification is limited because ODL transactions look like regular XRP payments on-chain.

Some analysts attempt to identify ODL flows by monitoring known ODL corridor exchange accounts, but this is imprecise. For valuation, we typically rely on Ripple's reports while noting the verification limitation.

---

Frequency Guidelines:

Real-time monitoring is needed for price data (if trading), major transaction alerts, and network status issues. Most investors don't need real-time data.

Daily collection should include transaction counts, active addresses, DEX volume, and exchange reserve changes. This provides trend data without excessive effort.

Weekly updates suit account growth metrics, development activity, and social sentiment indicators.

Monthly tracking covers escrow changes, holder distribution analysis, and detailed network statistics.

Quarterly reviews should incorporate Ripple's reports, full model updates, and comprehensive thesis review.

Build a structured tracking system:

Tab 1: Price Data - Date, OHLCV, source, timestamp. Maintain daily history.

Tab 2: On-Chain Metrics - Daily transactions, active addresses, fee burns, DEX volume. Calculate rolling averages.

Tab 3: Supply Dynamics - Circulating supply, escrow balance, monthly release/return. Track changes over time.

Tab 4: ODL Estimates - Quarterly volume from Ripple reports, implied daily average, quarter-over-quarter growth rates.

Tab 5: Comparables - Stellar metrics, Bitcoin/Ethereum benchmarks, traditional payment company data.

For Technical Users:

Python offers the xrpl-py library for direct XRPL queries, requests for API calls, pandas for data management, and schedule for automation. A simple script can collect daily metrics automatically.

Google Sheets can use IMPORTDATA functions for CSV feeds, various API connector add-ons, and scheduled triggers for automatic updates.

No-Code Options:

Dune Analytics provides pre-built dashboards for some XRPL metrics. CoinGecko allows CSV exports of price history. Manual weekly updates work fine for most individual investors.

---

Exchange Volume Inflation: Wash trading is common in crypto. Some exchanges report 10× their real volume. Use adjusted "real volume" estimates from CoinGecko or Messari when available.

Stale Data: APIs can lag, especially for free tiers. Always check timestamps and note data freshness in your analysis.

Methodology Changes: Platforms periodically change how they calculate metrics. This breaks historical comparisons. Document methodology used at time of collection.

Missing Data: Gaps exist in historical records, especially for newer metrics. Note limitations rather than interpolating.

Multiple Source Verification: Compare CoinGecko vs. CoinMarketCap pricing. Check exchange direct data vs. aggregators. Discrepancies warrant investigation.

Sanity Checks: Does reported volume make sense given market cap and historical patterns? Are growth rates plausible? Do trends align across related metrics?

Historical Consistency: Verify that historical data hasn't been revised. Check that your stored data matches current historical queries.

Example documentation: "ODL Volume Q3 2024: $1.8B. Source: Ripple Quarterly XRP Markets Report (October 2024). Retrieved: October 15, 2024. Note: Self-reported by Ripple, not independently verified. Adjusted: None."

This documentation enables future verification and helps identify issues when models produce unexpected results.

---

✅ On-chain data is verifiable - XRPL transactions are cryptographically confirmed and permanently recorded. This data is as reliable as blockchain technology allows.

✅ Multiple data sources exist - Between explorers, APIs, and analytics platforms, comprehensive XRP data is accessible to anyone willing to collect it.

✅ Ripple provides regular disclosures - Quarterly reports give ODL and escrow updates on a predictable schedule.

✅ Market data is available - Price, volume, and derivatives data is accessible from multiple providers.

⚠️ ODL volume accuracy - Ripple's quarterly reports are self-reported without independent audit. We must trust these figures or discount them.

⚠️ Real vs. wash trading volume - Exchange volume figures are often inflated. "Real" volume estimates are themselves estimates.

⚠️ Complete picture - Some XRP activity may occur off-chain or in ways not captured by available tools.

⚠️ Future data availability - Sources can change, discontinue, or start charging. Build flexibility into your infrastructure.

📌 Trusting single sources - Any single source can be wrong. Always verify important data across multiple sources.

📌 Ignoring methodology - The same metric (e.g., "active addresses") can be calculated differently by different providers.

📌 Stale data in models - Using outdated data leads to outdated conclusions. Verify freshness before major decisions.

📌 Over-precision - Don't treat rough estimates as exact figures. $1.8B ODL volume is an estimate, not a precise measurement.

XRP's data infrastructure is better than many altcoins but worse than traditional equities. On-chain data is reliable and verifiable. ODL data depends on Ripple's self-reporting. Market data requires wash-trading skepticism. Build a systematic data collection process, document everything, note limitations clearly, and update regularly. Your valuation is only as good as your data.

---

Assignment: Build your personal XRP data tracking system.

Requirements:

Part 1: Source Inventory (1 page)

• 10+ data sources you'll use
• What data each provides
• Your assessment of reliability (Tier 1/2/3)
• Access method (API, manual, subscription)
• Update frequency needed

Part 2: Tracking Spreadsheet (functional file)

• Price data tab (last 30 days minimum)
• On-chain metrics tab (transactions, addresses)
• Supply dynamics tab (escrow tracking)
• Comparables tab (at least Stellar)
• All sources cited in each tab

Part 3: Update Protocol (1 page)

• What you'll update and when (daily/weekly/monthly)
• How you'll validate data quality
• Where you'll store historical data
• How you'll handle source changes

Part 4: Limitations Analysis (1 page)

• What data you cannot get or verify

• Where data quality is questionable

• How these limitations affect your analysis

• What you'll do about gaps

• Source comprehensiveness (25%)

• Spreadsheet functionality (30%)

• Protocol practicality (20%)

• Limitations honesty (25%)

Time Investment: 3-4 hours

---

For Next Lesson:
With data infrastructure in place, we'll build your first actual XRP valuation model in Lesson 6: Building Your First XRP Model.

---

End of Lesson 5

Total words: ~5,800
Estimated completion time: 50 minutes reading + 3-4 hours for deliverable