Liquidity providers deposit funds into Azuro's pools. Bettors bet against the liquidity providers according to the odds set by the protocol. Bettors’ losses get shared between Azuro DAO (revenue), and LPs, frontend providers and data providers (supply-side fees).

This dashboard only tracks Azuro v1. Azuro is an infrastructure & liquidity layer for on-chain betting built on Polygon and Gnosis. Azuro was launched in 2021.

Azuro DAO owns and governs the protocol. They currently take a cut from the losses of the bettors (revenue). Azuro’s investors include Arrington Capital, Delphi Digital, Ethereal Ventures, Gnosis, Alliance DAO, and others.

github

twitter

discord

website

Prediction markets

Azuro

# Azuro Active users (daily) Methodology

## 1. Overview

Daily Active Users (DAU) for Azuro measures the number of unique wallet addresses that placed bets on the Azuro prediction markets protocol within a single day. This metric tracks user engagement by counting distinct bettor addresses across all supported chains and contract versions, providing insight into the protocol's daily user activity and adoption.

## 2. Data sources

The calculation uses the following raw data sources:
- **Blockchain events**: Parsed `NewBet` events from Azuro smart contracts deployed on Polygon and Gnosis chains
- **Contract versions**: Events from multiple Azuro protocol versions (v1 and v2) and contract types (Core contracts and LP1 liquidity provider contracts)
- **Transaction data**: Blockchain transaction metadata including block timestamps and transaction hashes for temporal attribution
- **Event parameters**: Bettor wallet addresses extracted from different parameter fields depending on contract version (`bettor`, `player`, `owner`)

## 3. Step-by-step calculation

### Component A: User event extraction
- **Purpose**: Identifies all betting activities across Azuro contracts to extract user addresses
- **Logic**: Extracts betting events from multiple Azuro contract deployments across Polygon and Gnosis chains. For Polygon, processes `NewBet` events from both v1 and v2 Core contracts, extracting bettor addresses from `bettor` parameter (v1) and `player` parameter (v2). For Gnosis, processes `NewBet` events from v1 Core contracts using `bettor` parameter and from v1 LP1 contracts using `owner` parameter. Each event is enriched with metadata including chain identifier, market sector classification as prediction markets, business segment as betting, and user type as Bettor.
- **Key fields**: Block timestamp for temporal attribution, transaction hash for deduplication, standardized `user_address` field mapped from various parameter names, and metadata fields for business classification

### Component B: Daily user aggregation
- **Purpose**: Converts individual betting events into daily distinct user counts
- **Logic**: Truncates block timestamps to daily boundaries using day-level granularity to establish consistent time windows. Groups all user events by the truncated daily timestamp along with chain, user type, and other metadata dimensions. Applies distinct aggregation to count unique user addresses within each day, ensuring that users who place multiple bets in a single day are only counted once.
- **Key fields**: Truncated `timestamp` field representing daily boundaries, distinct `user_dau` field containing unique user addresses per day, and preserved metadata fields for dimensional analysis

### Final aggregation
- **Combining components**: The daily user aggregation component directly processes the user event extraction results without additional joining, as both components are part of a sequential transformation pipeline
- **Currency conversion**: Not applicable as this metric measures user counts rather than monetary values
- **Time aggregation**: Uses day-level timestamp truncation to establish consistent daily boundaries, with each day representing a complete 24-hour period based on block timestamps
- **Final calculation**: The metric value represents the count of distinct wallet addresses that placed bets on any Azuro contract within each calendar day, filtered by chain availability to ensure data quality and completeness

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

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

AzuroAZUR

Archived

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown