Through the use of blockchain and modern APIs, Ripple enables financial institutions who are part of the network, RippleNet, to send money globally, instantly, reliably and for fractions of a penny. RippleNet is built on top of Ripple’s consensus ledger, XRP Ledger (XRPL).

Ripple is the leading provider of crypto-enabled solutions for businesses. Ripple was founded by Chris Larsen and Jed McCaleb and launched in 2012 (previously OpenCoin).

XRP tokenholders own and govern Ripple's consensus ledger 'XRP Ledger' (XRPL). Ripple's investors include a16z, Pantera Capital, Route 66 Ventures, etc.

github

twitter

website

Blockchains (L1)

XRP Ledger

# XRP Ledger Active users (weekly) Methodology

## 1. Overview

Active users (weekly) measures the number of unique addresses that execute transactions on the XRP Ledger within a 7-day rolling window. The metric tracks two distinct user types: transaction senders across all transaction types, and DEX traders who specifically interact with the XRP Ledger's decentralized exchange infrastructure. For DEX traders, users are further segmented by product: XRPL CLOB (the central limit order book) and XRPL AMM (automated market maker pools).

## 2. Data sources

- **Blockchain transactions**: Transaction records from the XRP Ledger, covering all transaction types for general user activity and specific transaction types (`OfferCreate`, `Payment`) for DEX trader identification

## 3. Step-by-step calculation

### Component A: Transaction sender identification

- **Purpose**: Capture all unique addresses that initiate any transaction on the XRP Ledger
- **Logic**: Extract the sender address from all transaction records regardless of transaction type. Aggregate unique addresses per 7-day window with UTC day boundaries.
- **Key fields**: `account` (sender address), `block_timestamp` (timing)

### Component B: XRPL CLOB trader identification

- **Purpose**: Identify users who trade on the central limit order book
- **Logic**: Parse transactions where the transaction type is `OfferCreate` and the result is `tesSUCCESS`, indicating successful limit order placement. Additionally, identify `Payment` transactions that modify or delete offer ledger entries, capturing trades executed through payment pathfinding. Aggregate unique addresses per 7-day window and tag with product identifier `XRPL CLOB`.
- **Key fields**: `transaction_type`, `transaction_result`, `ledger_entry_type`, `node_type`, `account` (trader address)

### Component C: XRPL AMM trader identification

- **Purpose**: Identify users who trade through automated market maker pools
- **Logic**: Join XRPL AMM reserve update records with transaction records to identify addresses executing swaps. Filter for `Payment` and `OfferCreate` transaction types with `tesSUCCESS` results, as these are the only transaction types that route trades through XRPL AMM pools. Aggregate unique addresses per 7-day window and tag with product identifier `XRPL AMM`.
- **Key fields**: `transaction_type`, `transaction_result`, `account` (trader address)

*This methodology was automatically generated by Token Terminal's methodology analyzer.*

Unique revenue-generating users over a rolling 7-day window.

XRP LedgerXRP

Active users (weekly)

Active users (weekly)

Competitive landscape