Validators process & store the uploaded data and collect upload & storage fees from data uploaders (supply-side fees).

Swarm is a data storage network built on Gnosis. Swarm was founded by Viktor Tron, Jeffrey Wilcke and Daniel A. Nagy and launched in 2016.

BZZ tokenholders own and govern the protocol. They currently don’t take a cut of the fees paid by data uploaders.

github

twitter

discord

etherscan

website

Infrastructure

Swarm

# Swarm Average fees per user (AFPU) Methodology

## 1. Overview

AFPU measures the average daily fee revenue generated per daily active user on the Swarm network. This metric answers the question: "How much fee revenue does each active user generate per day on average?" The calculation divides total daily fees by the count of daily active users, providing insight into user monetization efficiency and revenue per user trends on Swarm's decentralized storage network.

## 2. Data sources

The calculation relies on several key data sources:

- **Blockchain events**: Parsed Gnosis chain events from Swarm's PostageStamp contract, specifically `BatchCreated` and `BatchTopUp` events that track postage stamp purchases and top-ups
- **Transaction data**: Gnosis chain token transfer records to identify additional user interaction patterns  
- **External data**: End-of-day BZZ token price feeds for USD conversion and token metadata for decimal precision handling
- **Contract addresses**: Hardcoded PostageStamp contract address (`0x30d155478ef27ab32a1d578be7b84bc5988af381`) and BZZ token addresses for Gnosis (`0xdbf3ea6f5bee45c02255b2c26a16f300502f68da`) and Ethereum (`0x19062190b1925b5b6689d7073fdfc8c2976ef8cb`)

## 3. Step-by-step calculation

### Component A: Daily active users calculation

- **Purpose**: Identifies and counts unique users interacting with Swarm's postage stamp system daily
- **Logic**: Extracts user addresses from PostageStamp contract events on Gnosis chain. Identifies "Batch Creator" users from `BatchCreated` events using the `owner` parameter. Identifies "Batch TopUpper" users by joining `BatchTopUp` events with token transfer records where BZZ tokens are transferred to the PostageStamp contract address. All user interactions are timestamped and deduplicated by day. Uses HyperLogLog aggregation to efficiently count distinct users across multiple dimension breakdowns (project-level, chain-level, user-type-level, product-level)
- **Key fields**: `block_timestamp` for daily aggregation, `owner` field from batch creation events, `from_address` from token transfers for top-up identification, and calculated `user_address` field for distinct counting

### Component B: Daily fees calculation  

- **Purpose**: Calculates total daily fee revenue generated from postage stamp purchases and top-ups
- **Logic**: Extracts fee amounts from the same PostageStamp contract events. Captures `totalAmount` from `BatchCreated` events and `topupAmount` from `BatchTopUp` events, both denominated in BZZ tokens. Maps the chain context to Ethereum for price calculation purposes while preserving Gnosis as the real execution chain. Converts BZZ token amounts to USD using end-of-day price feeds and corrects for token decimal precision. Aggregates all fee amounts by day through summation
- **Key fields**: `totalAmount` and `topupAmount` fields containing BZZ token amounts, `token_address` for price feed lookup, corrected `amount` field after decimal adjustment, and final `fees` field in USD

### Final aggregation

- **Combining components**: Both user and fee metrics are aggregated to daily grain using timestamp truncation to day level. User counts use HyperLogLog merge operations to maintain distinct counting accuracy across dimension rollups. Fee amounts use standard summation aggregation  
- **Currency conversion**: BZZ token amounts converted to USD using end-of-day price feeds with proper decimal correction applied based on token metadata
- **Time aggregation**: All data aggregated to daily boundaries using timestamp truncation. Missing days filled with zeros to ensure continuous time series
- **Final calculation**: AFPU calculated by dividing total daily fees (in USD) by daily active user count. The division operation is handled by the ARPU calculation macro which safely manages division by zero scenarios and applies the zero-fill strategy for missing data points

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

SwarmBZZ

Average fees per user (AFPU)

Average fees per user (AFPU)

Competitive landscape