Players wager against the house (liquidity provided by BetSwirl or their partners) in randomized games of chance, such as coin tosses or dice rolls.

Betswirl is a non-custodial betting platform built on Polygon, BNB Chain, and Avalanche. BetSwirl was co-founded by Romuald Hog and Nato, and was launched in March 2022.

The BetSwirl team own and govern the protocol. They and BETS holders currently receive all fees paid by players (revenue).

github

twitter

discord

etherscan

website

Prediction markets

BetSwirl

# BetSwirl Supply-side fees Methodology

## 1. Overview

Supply-side fees represent payments made to game initiators in Betswirl's Russian Roulette prediction market. This metric captures the portion of house edge that is allocated to users who initiate games, compensating them for providing liquidity and game opportunities to other players. The calculation aggregates daily fees across all supported blockchains (Arbitrum, Avalanche, BSC, and Polygon) and converts all amounts to USD for consistent reporting.

## 2. Data sources

- **Blockchain events**: Parsed `RussianRoulette_AllocateHouseEdgeAmount_event` logs from Betswirl v1 contracts on Arbitrum, Avalanche, BSC, and Polygon
- **Transaction data**: Event logs containing house edge allocation details including amounts for dividends, treasury, team, and initiators
- **External data**: End-of-day token price feeds for USD conversion
- **Token metadata**: Token decimal information and symbol data for proper amount calculations
- **Contract addresses**: Wrapped token addresses (WETH, WAVAX, WBNB, WMATIC) and BETS token addresses on multiple chains

## 3. Step-by-step calculation

### Component A: Revenue allocation extraction
- **Purpose**: Extract house edge allocation events from Russian Roulette games across all supported chains
- **Logic**: Parse `RussianRoulette_AllocateHouseEdgeAmount_event` logs from Betswirl v1 contracts on Arbitrum, Avalanche, BSC, and Polygon. Extract the `dividend`, `treasury`, `team`, and `initiator` amounts along with token address and transaction metadata. Apply chain-specific labeling and categorize all activity under prediction markets business line and betting business segment.
- **Key fields**: `dividend_amount`, `treasury_amount`, `team_amount`, `initiator_amount`, `token_address`, `block_timestamp`, `chain`

### Component B: Daily aggregation and token mapping
- **Purpose**: Aggregate initiator amounts by day and apply token address standardization for pricing
- **Logic**: Group revenue allocation events by daily timestamps, chain, and token address. Sum the `initiator_amount` values to calculate daily supply-side fees. Apply token address mapping to handle native tokens by replacing null addresses with their wrapped equivalents (WETH for Arbitrum, WAVAX for Avalanche, WBNB for BSC, WMATIC for Polygon). Use special cross-chain mapping for BETS token, substituting Polygon BETS address when pricing Arbitrum BETS due to liquidity considerations.
- **Key fields**: `fees_supply_side` (sum of initiator amounts), `token_address` (mapped), `timestamp` (daily), `chain` and `real_chain`

### Final aggregation
- **Combining components**: Sum daily supply-side fees across all tokens and chains for each day
- **Currency conversion**: Convert token amounts to USD using end-of-day price feeds, applying decimal corrections based on token metadata
- **Time aggregation**: Aggregate to daily boundaries using timestamp truncation, with zero-filling for days without activity
- **Final calculation**: The final metric represents the total USD value of fees paid to game initiators each day, calculated as the sum of all `initiator_amount` values from house edge allocations, converted to USD and aggregated across all supported chains and tokens

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

Portion of fees distributed to service providers or supply-side participants.

BetSwirlBETS

Archived

Supply-side fees

Supply-side fees

Competitive landscape

Chain breakdown