OpenChat users can send messages to each other containing tokens such as ICP. Users can upgrade to Diamond membership to have access to extra or enhanced features.

OpenChat is a chat application running end-to-end on the Internet Computer blockchain.

CHAT tokenholders own and govern the protocol.

github

twitter

website

Social

OpenChat

# OpenChat Supply-side fees Methodology

## 1. Overview

OpenChat supply-side fees represent the portion of platform fees that would be distributed to users or content creators who contribute to the platform's value. However, OpenChat operates under a model where all fees are retained as protocol revenue, resulting in zero supply-side fees. This metric answers the question "How much revenue does OpenChat share with its user base?" with the answer being none - all diamond membership fees are considered protocol fees.

The calculation starts with diamond membership payment events from OpenChat's platform, processes them through standard fee calculation logic, then explicitly sets all supply-side fees to zero to reflect OpenChat's business model.

## 2. Data sources

- **Platform events**: OpenChat's event stream data from their `events_v4` API, containing user interactions and payment events on the Internet Computer blockchain
- **Payment events**: Specifically `diamond_membership_payment` events that capture premium membership purchases
- **Token price data**: End-of-day price feeds from CoinGecko for CHAT and ICP token USD conversion
- **Blockchain data**: Internet Computer network data where OpenChat operates as a decentralized social platform

## 3. Step-by-step calculation

### Component A: Event extraction and deduplication
- **Purpose**: Extract and clean diamond membership payment events from OpenChat's platform
- **Logic**: The system retrieves all events from OpenChat's event stream and filters specifically for `diamond_membership_payment` events. These events contain payment information for users purchasing premium memberships. To ensure data quality, the system deduplicates events by creating unique combinations of timestamp, user identifier, event name, source, and JSON payload content. A row number is assigned to each event within these partitions, and only the first occurrence (row_number = 1) is retained.
- **Key fields**: `timestamp` for event timing, `name` for event type filtering, `user` for payer identification, `source` for event origin, `payload` containing payment details

### Component B: Payment data parsing and processing
- **Purpose**: Extract payment details from JSON event payloads and prepare for USD conversion
- **Logic**: The system parses the JSON payload to extract key payment information including the payment `amount`, membership `duration`, `token` type (CHAT or ICP), and other payment characteristics like whether it's `manual_payment` or `recurring`. Token amounts are converted from their native precision of 1e8 to standard decimal format by dividing by 100,000,000. The system maps token symbols to their corresponding CoinGecko identifiers: CHAT tokens map to 'openchat' and ICP tokens map to 'internet-computer' for price lookup purposes.
- **Key fields**: `amount` (payment amount in tokens), `duration` (membership period), `token` (CHAT or ICP), `coingecko_id` (for price conversion)

### Component C: USD conversion and daily aggregation
- **Purpose**: Convert token payments to USD values and aggregate by day
- **Logic**: Using the CoinGecko identifiers, the system retrieves end-of-day token prices and converts payment amounts to USD values. The conversion uses standard Token Terminal methodology for currency conversion. Timestamps are truncated to day-level boundaries to create daily aggregations. Additional metadata is added including chain identifier ('internetcomputer'), market sector ('social'), and business segment ('social') classifications.
- **Key fields**: `fees` (USD-converted payment amounts), `daily_timestamp` (truncated to day), `chain_id` (blockchain identifier)

### Component D: Supply-side fee override
- **Purpose**: Set all supply-side fees to zero to reflect OpenChat's business model
- **Logic**: The system takes the calculated total fees from diamond membership payments and explicitly sets the `fees_supply_side` value to 0 for all records. This reflects OpenChat's business model where all premium membership fees are retained as protocol revenue rather than being shared with users or content creators who contribute to the platform's value.
- **Key fields**: `fees_supply_side` (always 0), inheriting timestamp and identification fields from total fees

### Final aggregation
- **Combining components**: The supply-side fees inherit the same time boundaries and chain identifications as the total fees calculation, but with fee amounts set to zero
- **Currency conversion**: All underlying fee calculations use end-of-day USD conversion rates from CoinGecko before the supply-side override
- **Time aggregation**: Daily boundaries are maintained through timestamp truncation to day-level precision
- **Final calculation**: Supply-side fees = 0 for all time periods and all diamond membership payment activity, regardless of the underlying total fee amounts

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

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

OpenChatCHAT

Supply-side fees

Supply-side fees

Competitive landscape