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 Unique person proof count Methodology

## 1. Overview

The unique person proof count metric measures the daily number of proof of uniqueness submissions on the OpenChat social platform. This metric tracks user verification activities within OpenChat's ecosystem, specifically counting instances where users submit proof of their uniqueness. The calculation aggregates daily counts of `proof_of_uniqueness_submitted` events from the OpenChat application running on the Internet Computer blockchain.

## 2. Data sources

- **OpenChat application events**: Event logs from the OpenChat social platform containing user interactions and system events
- **Internet Computer blockchain data**: Blockchain events and transactions from the Internet Computer network where OpenChat operates
- **User interaction data**: Application-level events capturing user activities, verifications, and proof submissions within the OpenChat ecosystem

## 3. Step-by-step calculation

### Component A: Event data preparation
- **Purpose**: Clean and deduplicate raw OpenChat event data
- **Logic**: Raw events from the OpenChat platform are processed to remove duplicates. Events are deduplicated based on combinations of `timestamp`, `user`, event `name`, `source`, and `payload` content. When multiple identical events exist, only the first occurrence is retained using row numbering within each partition group.
- **Key fields**: Event `timestamp` for timing, `name` for event type identification, `user` for user identification, `source` for event origin, and `payload` for additional event data

### Component B: Proof submission filtering
- **Purpose**: Identify and count proof of uniqueness submission events
- **Logic**: From the deduplicated events, filter to only include events where the event `name` equals `proof_of_uniqueness_submitted`. These events represent instances where users submit verification or proof of their uniqueness within the OpenChat platform.
- **Key fields**: Event `name` field used for filtering, `timestamp` for temporal tracking

### Final aggregation
- **Combining components**: The filtered proof submission events are grouped by daily timestamp boundaries using timestamp truncation to day level
- **Time aggregation**: Events are aggregated by calendar day, with each day representing a discrete measurement period
- **Metadata assignment**: Each daily count is enriched with categorical metadata including market sector (`social`), business segment (`social`), product identifier (null), and chain identifier (`internetcomputer`)
- **Gap handling**: The finalize metric process applies zero-fill strategy to ensure continuous daily time series, filling any missing days with zero counts
- **Final calculation**: The daily unique person proof count equals the total number of `proof_of_uniqueness_submitted` events occurring within each calendar day, after deduplication and filtering

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

Count of unique person-proof submissions.

OpenChatCHAT

Unique person proof count

Unique person proof count

Competitive landscape