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 Active users (daily) Methodology

## 1. Overview

Daily Active Users (DAU) for Swarm measures the number of unique user addresses that interact with the Swarm decentralized storage network's postage stamp system each day. This metric captures user engagement by identifying addresses that either create new postage stamp batches or top up existing batches, which are essential operations for using Swarm's storage services. The calculation focuses on infrastructure usage patterns to understand daily network adoption and utilization.

## 2. Data sources

The metric relies on the following raw data sources from Gnosis Chain:
- **Swarm PostageStamp contract events**: Parsed `PostageStamp_BatchCreated` and `PostageStamp_BatchTopUp` event logs from the PostageStamp contract (`0x30d155478ef27ab32a1d578be7b84bc5988af381`)
- **Token transfer records**: Gnosis Chain token transfer data filtered for BZZ token (`0xdbf3ea6f5bee45c02255b2c26a16f300502f68da`) transfers to the PostageStamp contract
- **Block and transaction metadata**: Gnosis Chain block timestamps and transaction identifiers for temporal correlation and deduplication

## 3. Step-by-step calculation

### Component A: Batch creator identification
- **Purpose**: Identifies users who create new postage stamp batches directly
- **Logic**: Extracts user addresses from parsed `PostageStamp_BatchCreated` event logs on Gnosis Chain. The `owner` field from these events represents the address creating the batch. Each interaction is classified as 'Batch Creator' user type and categorized under the 'infrastructure' market sector with 'other' business segment
- **Key fields**: Block timestamp (`block_timestamp`), transaction hash (`transaction_hash`), log index (`log_index`), and owner address (`owner`) from the event data

### Component B: Batch top-upper identification  
- **Purpose**: Identifies users who add funds to existing postage stamp batches
- **Logic**: Correlates BZZ token transfers with `PostageStamp_BatchTopUp` events by matching block timestamps. First, identifies BZZ token transfers directed to the PostageStamp contract address. Then joins these transfers with `PostageStamp_BatchTopUp` events that occurred in the same block. The sender address (`from_address`) of the token transfer represents the user topping up the batch. Each interaction is classified as 'Batch TopUpper' user type under the 'infrastructure' market sector
- **Key fields**: Block timestamp from both transfer and event data, transaction hash, log index, and sender address (`from_address`) from the token transfer

### Final aggregation
- **Combining components**: Union all batch creator and batch top-upper interactions into a single dataset, maintaining distinct user type classifications and temporal information
- **Time aggregation**: Apply daily boundaries by truncating block timestamps to day level using the `timestamp_trunc` function with 'day' granularity
- **Final calculation**: Count distinct user addresses per day while preserving user type, chain, and classification metadata. The result represents the number of unique addresses that performed any Swarm postage stamp operation on each day, with separate tracking for creators versus top-uppers

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

Unique revenue-generating users over a fixed 24-hour window.

SwarmBZZ

Active users (daily)

Active users (daily)

Competitive landscape