website

twitter

discord

github

basescan

Asset management

Mamo

# Mamo Active users (weekly) Methodology

## 1. Overview

Active users (weekly) measures the number of unique addresses that make a revenue-generating transaction with a project, i.e. An application or a blockchain. For Mamo, unique user interactions are captured across Mamo V1, Mamo V2, and Mamo Staking. Strategy owners are identified through contract deployment events, and their subsequent deposit and withdrawal activities are recorded. Staking and unstaking actions are also monitored to capture utility. Unique addresses are aggregated over a 7-day rolling window to evaluate weekly protocol engagement.

## 2. Data sources

- **Blockchain events**: `Deposit` and `Withdraw` events from `ERC20MoonwellMorphoStrategy` and `MoonwellMorphoStrategy` contracts, `StrategyCreated` events from `ERC20MoonwellMorphoStrategyFactory` contracts, and ERC-20 `Transfer` events for the MAMO asset, covering Base

## 3. Step-by-step calculation

### Component A: Mamo V1 and Mamo V2 strategy activity tracking

- **Purpose**: Identify active users interacting with Mamo V1 and Mamo V2 yield strategies
- **Logic**: Strategy mapping is established by parsing `StrategyCreated` events from `ERC20MoonwellMorphoStrategyFactory` contracts to link each strategy address to its owner. `Deposit` and `Withdraw` events are then extracted from `ERC20MoonwellMorphoStrategy` (for Mamo V1) and `MoonwellMorphoStrategy` (for Mamo V2) contracts. These activity events are joined with the strategy mapping to attribute the transactions to the respective strategy owners.
- **Key fields**: `block_timestamp` (timing), `address` (strategy address), `user_address` (strategy owner)

### Component B: Mamo Staking activity tracking

- **Purpose**: Identify active users staking or unstaking the MAMO asset
- **Logic**: ERC-20 `Transfer` events for the MAMO asset are filtered to isolate transactions involving the MAMO staking contract. For transfers directed to the staking contract, the sender address is classified as the active staker. For transfers originating from the staking contract, the recipient address is classified as the active unstaker.
- **Key fields**: `block_timestamp` (timing), `from_address` (sender), `to_address` (recipient), `value` (transfer amount)

### Component C: Weekly aggregation and deduplication

- **Purpose**: Consolidate active addresses and calculate weekly unique users
- **Logic**: All identified user addresses from strategy deposits, strategy withdrawals, and staking transfers are combined into a single dataset. Timestamps are truncated to weekly boundaries. Unique user addresses are then aggregated and deduplicated per 7-day window to calculate the final active users (weekly) metric.
- **Key fields**: `block_timestamp` (timing), `user_address` (user address)

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

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

MamoMAMO

Active users (weekly)

Active users (weekly)

Competitive landscape