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 P2P swap count Methodology

## 1. Overview

The P2P swap count metric measures the daily number of completed peer-to-peer token swaps within the OpenChat social platform on the Internet Computer blockchain. This metric quantifies user engagement in decentralized trading activities within the social application, tracking successful swap transactions between users. The calculation aggregates individual swap completion events by day to provide insights into trading activity and platform utilization.

## 2. Data sources

The calculation relies on the following data sources:
- **OpenChat application events**: Structured event logs from the OpenChat social platform on Internet Computer that capture user interactions and platform activities
- **P2P swap completion events**: Specific event records that indicate successful peer-to-peer token exchanges between OpenChat users
- **Internet Computer event data**: Blockchain-level event logs from the Internet Computer network containing OpenChat platform activities

## 3. Step-by-step calculation

### Component A: Event data extraction and deduplication
- **Purpose**: Extract and clean raw OpenChat event data to ensure data quality
- **Logic**: Raw event data is extracted from OpenChat's event logging system on Internet Computer. The system applies deduplication logic to handle potential duplicate events by creating unique fingerprints based on event `timestamp`, `user`, event `name`, `source`, and `payload` content. Events are ranked using row numbering within each partition of identical event characteristics, and only the first occurrence of each unique event is retained.
- **Key fields**: `timestamp` (event occurrence time), `name` (event type identifier), `user` (user identifier), `source` (event source), `payload` (event data)

### Component B: P2P swap event filtering and aggregation
- **Purpose**: Identify completed P2P swaps and aggregate them by day
- **Logic**: The deduplicated event data is filtered to include only events where the `name` field equals 'p2p_swap_completed', which represents successful peer-to-peer token exchanges. These filtered events are then grouped by day using timestamp truncation to daily boundaries. The system counts the total number of swap completion events for each day and applies consistent metadata including social sector classification and Internet Computer chain identification.
- **Key fields**: `p2p_swap_count` (daily count of completed swaps), `timestamp` (daily boundary), `chain_id` (Internet Computer identifier)

### Final aggregation
- **Combining components**: The filtered and counted P2P swap events are processed through a finalization macro that standardizes the metric schema and ensures data quality
- **Currency conversion**: Not applicable for this count-based metric
- **Time aggregation**: Events are aggregated into daily boundaries using timestamp truncation, with each day representing a complete 24-hour period
- **Final calculation**: The final metric represents the total count of unique P2P swap completion events that occurred within each day on the OpenChat platform, with gap-filling applied to ensure continuous daily coverage using zero values for days without swap activity

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

OpenChatCHAT

P2P swap count

P2P swap count

Competitive landscape