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 Trading volume Methodology

## 1. Overview

Azuro trading volume measures the total USD value of bets placed on Azuro's prediction markets platform on a daily basis. This metric captures betting activity across multiple blockchain networks and protocol versions, providing insight into user engagement and capital flow within Azuro's decentralized prediction markets ecosystem. The calculation aggregates bet amounts from blockchain events, converts them to USD, and ensures complete daily time series data.

## 2. Data sources

The calculation uses the following raw data sources:
- **Blockchain events**: Parsed `NewBet` event logs from Azuro smart contracts deployed on Polygon and Gnosis chains
- **Contract events**: Events from multiple Azuro contract types including `FactoryCreatedCore`, `Core`, and `LP1` contracts across protocol versions v1 and v2
- **Token transactions**: Native token amounts from betting transactions in USDC (Polygon v1), USDT (Polygon v2), and WXDAI (Gnosis v1)
- **External data**: End-of-day price feeds for USDC, USDT, and WXDAI tokens for USD conversion
- **Token metadata**: Token decimal specifications for proper amount normalization

## 3. Step-by-step calculation

### Component A: Raw betting event extraction
- **Purpose**: Extract and standardize betting events from multiple Azuro contract deployments across different blockchains and protocol versions
- **Logic**: The system collects `NewBet` events from four distinct sources: Azuro v1 `FactoryCreatedCore` contracts on Polygon (using USDC), Azuro v2 `Core` contracts on Polygon (using USDT), Azuro v1 `Core` contracts on Gnosis (using WXDAI), and Azuro v1 `LP1` contracts on Gnosis (using WXDAI). Each event is enriched with standardized metadata including chain identifier, protocol version, and business classification
- **Key fields**: `block_timestamp` for timing, `transaction_hash` and `log_index` for uniqueness, `amount` for bet size, and `token_address` for the specific token used in each bet

### Component B: Business metadata standardization
- **Purpose**: Apply consistent business categorization and metadata to all betting events regardless of source
- **Logic**: All betting events are classified with uniform business metadata: business line as "Prediction markets", market sector as "prediction_markets", and business segment as "betting". Protocol version and chain information are preserved from the source contracts, while product ID is left null as Azuro operates as a single prediction markets platform
- **Key fields**: `business_line`, `market_sector_id`, `business_segment_id`, `version`, and `chain` for business intelligence and filtering

### Component C: Daily aggregation and timestamping
- **Purpose**: Aggregate individual betting events into daily trading volume totals while preserving dimensional metadata
- **Logic**: Betting events are grouped by day using timestamp truncation of the original block timestamps. The aggregation preserves all dimensional attributes including chain, business metadata, token address, and protocol version while summing the betting amounts
- **Key fields**: `timestamp` truncated to day boundaries, `trading_volume` as the sum of betting amounts, and all dimensional fields for grouping and analysis

### Component D: Currency conversion and decimal correction
- **Purpose**: Convert native token amounts to standardized USD values with proper decimal handling
- **Logic**: The system applies decimal correction based on each token's specification (USDC has 6 decimals, USDT has 6 decimals, WXDAI has 18 decimals) and then converts to USD using end-of-day price feeds. This ensures consistent USD valuation regardless of the underlying token used for betting
- **Key fields**: `trading_volume` converted from native token units to USD with proper decimal adjustment

### Final aggregation
- **Combining components**: Daily betting volumes are maintained with full dimensional detail including chain, token, and business metadata
- **Currency conversion**: All amounts are converted to USD using end-of-day token prices applied after decimal correction
- **Time aggregation**: Daily boundaries are established using block timestamp truncation to day level
- **Final calculation**: The final trading volume represents the total USD value of all bets placed on Azuro prediction markets for each day, with zero-filling applied to ensure complete daily time series and chain availability filters ensuring data quality consistency

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

Total value of spot trades executed on the exchange.

AzuroAZUR

Archived

Trading volume

Trading volume

Competitive landscape

Chain breakdown