# Constant Product rex33 supply Methodology

## 1. Overview

rex33 supply measures the total number of rex33 tokens in circulation within the Constant Product environment. This metric represents the aggregate balance of receipt assets held by users, which are issued upon depositing collateral and retired upon withdrawal. Tracking the circulating supply is essential for understanding the scale of liquidity and participation within the Etherex ecosystem.

## 2. Data sources

- **Blockchain events**: `Deposit` and `Withdraw` events from `rex33` contracts, covering Linea
- **External data**: Asset metadata for decimal normalization

## 3. Step-by-step calculation

### Component A: Mint and burn event capture

- **Purpose**: Identify all transactions that increase or decrease the circulating supply of rex33 assets
- **Logic**: `Deposit` and `Withdraw` events are parsed from `rex33` contracts. The quantities of shares specified in `Deposit` events are classified as mints (supply increases), while shares specified in `Withdraw` events are classified as burns (supply decreases). Events marked as removed due to chain reorganizations are excluded from the dataset.
- **Key fields**: `block_timestamp` (timing), `in_shares` (share quantity), `address` (asset identification)

### Component B: Daily net change calculation

- **Purpose**: Aggregate granular event data into daily supply deltas
- **Logic**: All mint and burn actions are aggregated by day, chain, and asset. A daily net delta is calculated by subtracting the total burned share volume from the total minted share volume for each UTC day.
- **Key fields**: `block_timestamp` (day truncation), `amount` (net change)

### Component C: Cumulative supply tracking

- **Purpose**: Determine the total outstanding balance of assets over time
- **Logic**: A running total of the daily net deltas is calculated chronologically. This cumulative sum represents the total outstanding supply of the rex33 asset at the end of each day, reflecting the history of all mints and burns since inception.

### Component D: Normalization and temporal alignment

- **Purpose**: Ensure data accuracy through decimal correction and continuous reporting
- **Logic**: Raw asset quantities are normalized by decimal precision using asset metadata. To maintain a consistent time series, a forward-fill mechanism is applied where the most recent calculated supply balance is carried forward to subsequent days that lack transaction activity. The final values are zero-filled if no historical data exists for a given period.

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

rex33 supply

Constant Product

Archived

rex33 supply

rex33 supply