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 Revenue Methodology

## 1. Overview

Swarm revenue represents the USD value of revenue generated by the Swarm decentralized storage protocol. Currently, this metric is set to zero across all time periods, indicating that while Swarm collects fees through its postage stamp system, these fees do not constitute protocol revenue. The calculation leverages the same data infrastructure used for fee tracking but overrides all values to zero.

## 2. Data sources

The methodology uses the following raw data sources:
- **Swarm contract events**: Parsed `BatchCreated` and `BatchTopUp` events from the PostageStamp contract on Gnosis chain
- **Token price feeds**: End-of-day BZZ token price data from Ethereum markets  
- **Token metadata**: BZZ token decimal precision and conversion factors
- **Chain mapping data**: Configuration data for cross-chain price calculations

## 3. Step-by-step calculation

### Component A: Swarm fee event extraction
- **Purpose**: Extracts raw fee payment data from Swarm's postage stamp system
- **Logic**: Identifies `BatchCreated` events with `totalAmount` field and `BatchTopUp` events with `topupAmount` field from the PostageStamp contract on Gnosis chain. Maps these events to use Ethereum chain identifier for price calculation purposes while preserving the original Gnosis chain information. Classifies all fees under the Infrastructure business line and infrastructure market sector.
- **Key fields**: `totalAmount` and `topupAmount` representing BZZ token amounts paid for postage stamps, `block_timestamp` for timing, `transaction_hash` and `log_index` for event identification

### Component B: Fee processing and USD conversion  
- **Purpose**: Converts raw BZZ token amounts to standardized USD values
- **Logic**: Applies BZZ token decimal correction to normalize token amounts to standard precision. Performs USD conversion using end-of-day BZZ token prices from Ethereum markets. Truncates timestamps to daily boundaries and aggregates by day, chain, market sector, business segment, and product dimensions. Applies gap-filling logic to ensure continuous daily coverage.
- **Key fields**: `fees` representing daily USD fee amounts, `timestamp` for daily aggregation boundaries, `chain_id` for chain identification

### Component C: Revenue override calculation
- **Purpose**: Generates the final revenue metric by overriding fee amounts with zero values
- **Logic**: Takes the complete fee calculation structure including timestamps, chain identifiers, and dimensional breakdowns, but replaces all fee amounts with zero values. This maintains the same schema and temporal coverage as the fees metric while indicating that current fee collection does not represent protocol revenue.
- **Key fields**: `revenue` field set to zero across all records, maintaining same dimensional structure as fees

### Final aggregation
- **Combining components**: Uses the fees table structure as a template but overrides all monetary values to zero
- **Currency conversion**: No conversion needed as all values are set to zero USD
- **Time aggregation**: Maintains daily grain aggregation matching the fees calculation
- **Final calculation**: Revenue = 0 for all time periods and dimensional breakdowns, indicating Swarm currently generates no protocol revenue despite collecting fees

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

fees * take_rate (illustrative — revenue is observed directly per project, not derived from take_rate)

Fee revenue retained after supply-side payouts. Before cost of revenue (e.g. L2 DA fees) and before operating expenses.

SwarmBZZ

Revenue

Revenue

Competitive landscape