github

twitter

discord

etherscan

website

Liquid staking

Origin Protocol

# Origin Protocol Active users (monthly) Methodology

## 1. Overview

Monthly Active Users (MAU) measures the number of distinct users who interact with Origin Protocol's products within a 30-day rolling window. This metric tracks user engagement across Origin's ecosystem of stablecoins and yield-bearing tokens including Origin Dollar (Origin Dollar), OETH (Origin Ether), superOETHb (Base version), and OS (Sonic version). The calculation uses HyperLogLog data structures to efficiently count distinct users across multiple blockchain networks and provides dimensional breakdowns by chain, user interaction type, and product.

## 2. Data sources

The calculation relies on the following blockchain data sources:

- **Ethereum blockchain events**: Parsed events from Origin Protocol smart contracts including `Vault_Mint`, `Vault_Redeem`, `OETHVault_Mint`, `OETHVault_Redeem`, `ZapperLidoARM_Zap`, `LidoARM_RedeemClaimed`, and `OETHZapper_Zap` events that capture Origin Dollar and OETH interactions
- **Base blockchain events**: Parsed events from Origin Protocol contracts including `superOETHbVault_Mint`, `superOETHbVault_Redeem`, and `superOETHbZapper_Zap` events for superOETHb token interactions
- **Sonic blockchain events**: Parsed events from Origin Protocol contracts including `OSVault_Mint`, `OSVault_Redeem`, and `OSZapper_Zap` events for OS token interactions  
- **Arbitrum blockchain function calls**: Successful function calls to Origin Protocol contracts, specifically `wOETH_burn` functions for wrapped OETH interactions
- **Ethereum blockchain function calls**: Successful function calls to Origin Protocol's Flipper contract including `sellOusdForDai`, `sellOusdForUsdt`, `sellOusdForUsdc`, `buyOusdWithDai`, `buyOusdWithUsdc`, and `buyOusdWithUsdt` functions for Origin Dollar trading

## 3. Step-by-step calculation

### Component A: User interaction extraction
- **Purpose**: Extract and classify all user interactions with Origin Protocol contracts across multiple blockchains
- **Logic**: Parse blockchain events and successful function calls from Origin Protocol smart contracts across Ethereum, Base, Arbitrum, and Sonic networks. Extract user addresses from various event parameters including `_addr`, `sender`, `withdrawer`, `minter`, and `from_address` fields depending on the specific contract interaction. Classify users based on their interaction type such as Origin Dollar minter, Origin Dollar redeemer, OETH minter, OETH redeemer, ARM depositor, ARM redeemer, superOETHb minter, superOETHb redeemer, OS minter, OS redeemer, Flipper Origin Dollar seller, Flipper Origin Dollar buyer, woETH minter, and woETH burner
- **Key fields**: Extract `block_timestamp` for timing, `transaction_hash` for uniqueness, `chain` identifier, `user_type` classification, and `user_address` as the primary user identifier

### Component B: Daily active user aggregation  
- **Purpose**: Calculate daily distinct active users using efficient HyperLogLog data structures
- **Logic**: Group user interactions by day using `timestamp_trunc` on block timestamps. Create distinct daily active user counts grouped by timestamp, chain, user type, and product. Initialize HyperLogLog sketches for each daily grouping to enable memory-efficient distinct user counting across the subsequent rolling window calculations. Filter data based on chain availability to ensure only supported blockchain networks are included
- **Key fields**: Generate `timestamp` (truncated to day), `timestamp_grain` (set to 'day'), `chain`, `user_type`, `product_id`, and `user_dau` containing the user address

### Component C: Rolling window creation
- **Purpose**: Create 30-day sliding windows for monthly active user calculation
- **Logic**: Generate a complete datespine covering all days from the minimum timestamp in the daily active user data to the current date minus one day. For each day in the datespine, create a 30-day lookback window that includes the previous 29 days plus the current day. This is accomplished by generating timestamp arrays and joining each target day with its corresponding 30-day period. Join the window data with daily HyperLogLog sketches to prepare for aggregation
- **Key fields**: Maintain `timestamp` as the target date, preserve dimensional fields `chain_id`, `user_type`, `product_id`, and carry forward the HyperLogLog sketches `hll` from daily calculations

### Component D: Dimensional MAU calculation
- **Purpose**: Calculate monthly active users across different dimensional breakdowns
- **Logic**: For each dimensional breakdown, merge HyperLogLog sketches within each 30-day window using `hll_count.merge_partial` to combine daily distinct user counts, then extract the final distinct count using `hll_count.extract`. Create four separate dimensional views: project-level MAU aggregating all users regardless of chain, user type, or product; chain-level MAU broken down by blockchain network; user type-level MAU broken down by interaction classification; and product-level MAU broken down by Origin Protocol product
- **Key fields**: Generate `user_mau` as the final distinct monthly active user count, maintain `timestamp`, `timestamp_grain`, add `dimensions` field to identify the breakdown type, and preserve relevant dimensional fields while setting others to null

### Final aggregation
- **Combining components**: Union all dimensional breakdowns (project-level, chain-level, user type-level, and product-level) into a single result set using `UNION ALL` operations
- **Schema standardization**: Apply the `finalize_metric_user_mau` macro to standardize the output schema, add metadata fields, and implement a fill-zeros strategy for missing days
- **Time boundaries**: Filter results to include only data within the appropriate incremental processing window, using monthly partitioning for efficient processing
- **Final calculation**: The final `user_mau` value represents the count of distinct user addresses that interacted with Origin Protocol contracts within any 30-day rolling period, calculated using merged HyperLogLog sketches for memory efficiency and accuracy

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

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

Origin ProtocolOGN

Active users (monthly)

Active users (monthly)

Competitive landscape

Chain breakdown