Telecom Data Model

High-level entity-relationship model for DePIN telecom networks.

Core Principle

Data flows where value flows. In traditional telecom, carriers own the data. In DePIN telecom, the network generates shared, verifiable data that enables new value creation.

See Telecom Principles for the immutable truths this model serves.

Entity Domains

┌─────────────────────────────────────────────────────────────────────────────┐
│                           TELECOM DATA MODEL                                 │
├─────────────────────────────────────────────────────────────────────────────┤
│                                                                             │
│  ┌─────────────┐    ┌─────────────┐    ┌─────────────┐    ┌─────────────┐  │
│  │   INFRA     │    │  NETWORK    │    │  ECONOMIC   │    │   TRUST     │  │
│  │   DOMAIN    │    │   DOMAIN    │    │   DOMAIN    │    │   DOMAIN    │  │
│  └──────┬──────┘    └──────┬──────┘    └──────┬──────┘    └──────┬──────┘  │
│         │                  │                  │                  │          │
│         ▼                  ▼                  ▼                  ▼          │
│    Hotspots           Coverage           Tokens            Attestations    │
│    Antennas           Sessions           Rewards           Proofs          │
│    Backhaul           Traffic            Credits           Reputation      │
│    Locations          Quality            Settlements       Compliance      │
│                                                                             │
└─────────────────────────────────────────────────────────────────────────────┘

Entity Relationship Diagram

                                    ┌──────────────┐
                                    │   OPERATOR   │
                                    │──────────────│
                                    │ wallet_addr  │
                                    │ reputation   │
                                    │ stake_amount │
                                    └──────┬───────┘
                                           │
                          ┌────────────────┼────────────────┐
                          │ owns           │ earns          │ stakes
                          ▼                ▼                ▼
                   ┌──────────────┐ ┌──────────────┐ ┌──────────────┐
                   │   HOTSPOT    │ │    REWARD    │ │    TOKEN     │
                   │──────────────│ │──────────────│ │──────────────│
                   │ device_id    │ │ epoch        │ │ token_type   │
                   │ location     │ │ amount       │ │ total_supply │
                   │ status       │ │ reward_type  │ │ burn_rate    │
                   │ antenna_gain │ │ timestamp    │ │ price        │
                   └──────┬───────┘ └──────────────┘ └──────┬───────┘
                          │                                 │
           ┌──────────────┼──────────────┐                 │
           │ provides     │ witnesses    │                 │ burned_for
           ▼              ▼              ▼                 ▼
    ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐
    │   COVERAGE   │ │    PROOF     │ │   SESSION    │ │ DATA_CREDIT  │
    │──────────────│ │──────────────│ │──────────────│ │──────────────│
    │ hex_id       │ │ challenge_id │ │ session_id   │ │ amount       │
    │ signal_str   │ │ beacon_tx    │ │ start_time   │ │ dc_per_byte  │
    │ coverage_rad │ │ witnesses[]  │ │ end_time     │ │ burned_at    │
    │ last_update  │ │ validity     │ │ bytes_tx     │ │ purpose      │
    └──────┬───────┘ └──────────────┘ └──────┬───────┘ └──────────────┘
           │                                 │
           │ serves                          │ used_by
           ▼                                 ▼
    ┌──────────────┐                  ┌──────────────┐
    │     USER     │◄─────────────────│    DEVICE    │
    │──────────────│    connects      │──────────────│
    │ user_id      │                  │ device_id    │
    │ plan_type    │                  │ device_type  │
    │ data_credits │                  │ last_seen    │
    │ usage_hist   │                  │ data_used    │
    └──────────────┘                  └──────────────┘

Core Entities

Infrastructure Domain

Entity	Description	Key Attributes	Relationships
Operator	Entity that deploys and maintains hotspots	wallet_addr, reputation_score, stake_amount, location	owns Hotspots, earns Rewards, stakes Tokens
Hotspot	Physical device providing network coverage	device_id, location (lat/long/h3), status, antenna_gain, elevation	owned_by Operator, provides Coverage, witnesses Proofs
Antenna	Radio equipment attached to hotspot	type, gain_dbi, direction, height	attached_to Hotspot
Location	Geographic position with H3 hex indexing	h3_index, lat, long, elevation, terrain_type	contains Hotspots, defines Coverage

Network Domain

Entity	Description	Key Attributes	Relationships
Coverage	Geographic area with usable signal	hex_id, signal_strength, coverage_radius, last_verified	provided_by Hotspot, serves Users
Session	Active data transfer connection	session_id, start_time, end_time, bytes_transferred, quality_score	uses Hotspot, consumes Data_Credits
Traffic	Aggregated network usage data	period, total_bytes, unique_users, avg_latency	aggregates Sessions
Quality	Service quality measurements	latency_ms, packet_loss, jitter, uptime_pct	measured_for Hotspot, Session

Economic Domain

Entity	Description	Key Attributes	Relationships
Token	Network cryptocurrency (HNT, MOBILE)	token_type, total_supply, circulating, burn_rate, price_usd	earned_by Operators, burned_for Data_Credits
Reward	Token distribution to operators	epoch, amount, reward_type (coverage/data/witness), timestamp	earned_by Operator, paid_in Token
Data_Credit	Usage token (fixed USD price)	amount, dc_per_byte, burned_at, purpose	burned_from Token, consumed_by Session
Settlement	Inter-carrier payment record	settlement_id, parties[], amount, settlement_time, status	settles Traffic between Carriers

Trust Domain

Entity	Description	Key Attributes	Relationships
Proof	Coverage verification record	challenge_id, challenger, beacon_tx, witnesses[], validity, timestamp	proves Coverage, witnessed_by Hotspots
Attestation	Quality claim with cryptographic proof	attestation_id, claim_type, claim_value, signature, timestamp	attests Quality, signed_by Operator
Reputation	Operator trust score	operator_id, score, factors[], history[]	scored_for Operator
Compliance	Regulatory compliance record	jurisdiction, requirement, status, evidence[]	applies_to Operator, Hotspot

Key Relationships

The Coverage Loop

Operator deploys Hotspot
        ↓
Hotspot provides Coverage
        ↓
Coverage serves Users
        ↓
Users create Sessions
        ↓
Sessions burn Data_Credits
        ↓
Data_Credits burn Tokens
        ↓
Protocol mints Rewards
        ↓
Rewards paid to Operator
        ↓
Operator deploys more Hotspots

The Verification Loop

Hotspot receives Challenge
        ↓
Hotspot transmits Beacon
        ↓
Nearby Hotspots Witness
        ↓
Witnesses submit Proofs
        ↓
Protocol validates Proofs
        ↓
Valid Proof generates Reward
        ↓
Invalid Proof reduces Reputation

Data Flow Patterns

Real-Time Flows

Flow	Source	Destination	Frequency	Purpose
Coverage beacon	Hotspot	Witnesses	Per challenge	Proof of coverage
Session data	Device	Hotspot	Continuous	Usage metering
Quality metrics	Hotspot	Oracle	Per minute	QoS monitoring
Reward calculation	Protocol	Operator	Per epoch	Incentive distribution

Batch Flows

Flow	Source	Destination	Frequency	Purpose
Traffic aggregation	Sessions	Analytics	Hourly	Demand forecasting
Settlement calculation	Traffic	Carriers	Daily	Inter-carrier billing
Reputation update	Proofs	Operators	Per epoch	Trust scoring
Coverage mapping	Proofs	Coverage DB	Continuous	Network visualization

Traditional vs DePIN Data Model

Aspect	Traditional Carrier	DePIN Network
Ownership	Carrier owns all data	Shared, on-chain
Access	Siloed, proprietary	Open, permissioned
Verification	Self-reported	Cryptographic proofs
Latency	Batch (monthly)	Real-time
Trust model	Contracts, SLAs	Verification, reputation
Settlement	30-90 days	Atomic, instant

Implementation Considerations

On-Chain vs Off-Chain

Data	On-Chain	Off-Chain	Rationale
Hotspot registration	✓		Ownership proof
Coverage proofs	✓		Verification
Token transfers	✓		Settlement
Session details		✓	Volume, privacy
Quality metrics		✓ (oracle)	Frequent updates
Traffic analytics		✓	Aggregation

Indexing Strategy

Entity	Primary Index	Secondary Indexes	Query Pattern
Hotspot	device_id	location (H3), operator	Lookup, geo-query
Coverage	hex_id	signal_strength	Geo-query, filtering
Session	session_id	user_id, hotspot_id, time	Lookup, aggregation
Reward	epoch + operator	reward_type	Time-series, aggregation

Context

Telecom Principles — Immutable truths this model serves
Network MEV — Routing optimization algorithm
Information Arbitrage — The principle behind MEV
Data Flow — General data value principles

Core Principle​

Entity Domains​

Entity Relationship Diagram​

Core Entities​

Infrastructure Domain​

Network Domain​

Economic Domain​

Trust Domain​

Key Relationships​

The Coverage Loop​

The Verification Loop​

Data Flow Patterns​

Real-Time Flows​

Batch Flows​

Traditional vs DePIN Data Model​

Implementation Considerations​

On-Chain vs Off-Chain​

Indexing Strategy​

Context​