Skip to main content

​
Linkr Network

The Linkr Network is the coordination layer that connects users to hotspots and manages the flow of data across the system. It consists of client applications, backend services, and the protocol logic that governs how hotspots are verified, discovered, and rewarded.

​
Components

​
Client Applications

Linkr provides applications for both mobile and web:
  • Mobile App (iOS and Android): Primary interface for users and operators. Handles hotspot discovery, connection management, and operator dashboards.
  • Web App: Browser-based access to the coverage map, account management, and detailed analytics for operators.
Both applications communicate with the backend through the Linkr API.

​
Backend Services

The backend consists of several interconnected services:
ServiceResponsibility
API GatewayHandles all client requests, authentication, and rate limiting
Hotspot RegistryStores hotspot metadata, verification status, and configuration
Coverage EngineComputes coverage estimates and maintains the global map
Telemetry ProcessorIngests and processes real-time data from hotspots
Rewards EngineCalculates and distributes rewards based on performance metrics
Session ManagerTracks active user sessions and connection state

​
Protocol Layer

The protocol defines the rules for:
  • How hotspots report their status and telemetry
  • How coverage data is aggregated and validated
  • How rewards are calculated and distributed
  • How disputes and anomalies are handled

​
Data Synchronization

The Linkr Network continuously synchronizes data between hotspots, users, and the central services.

​
Hotspot to Network

Hotspots periodically report:
  • Heartbeat: A simple “I’m alive” signal sent every 60 seconds
  • Telemetry: Performance metrics including bandwidth, latency, and connection counts
  • Events: Significant state changes (restarts, configuration updates, errors)
{
  "hotspot_id": "hs_7xk2m9p4",
  "timestamp": "2024-01-15T14:32:00Z",
  "type": "telemetry",
  "data": {
    "uptime_seconds": 86400,
    "active_connections": 3,
    "bandwidth_mbps": 45.2,
    "latency_ms": 12
  }
}

​
Network to Hotspot

The network can push configuration updates and commands to hotspots:
  • Configuration: Network name, access policies, bandwidth limits
  • Commands: Restart, run diagnostics, update firmware
  • Challenges: Proof-of-availability requests for rewards validation

​
Network to User

Users receive:
  • Coverage data: Real-time map updates with hotspot availability
  • Connection credentials: Temporary access tokens for authenticated sessions
  • Session state: Active connection status and usage metrics

​
Coverage Computation

The Coverage Engine aggregates data from multiple sources to build an accurate picture of network coverage:
  1. Static data: Hotspot location, device specifications, reported range
  2. Dynamic data: Real-time availability, current load, recent performance
  3. Historical data: Uptime patterns, reliability trends, user reports
Coverage is represented as overlapping circles on the map, with color coding to indicate signal strength and quality.
Coverage estimates are probabilistic. The map shows where you are likely to find usable signal, but actual connectivity depends on local conditions.

​
Offline Behavior

The Linkr apps are designed to handle intermittent connectivity:
  • Cached map data: Recent coverage data is stored locally for offline viewing
  • Queued actions: Operations like hotspot registration queue locally and sync when online
  • Graceful degradation: The app remains functional with limited features when offline

​
Integration Points

Third-party developers can integrate with the Linkr Network through:
  • REST API: Query coverage data, manage hotspots programmatically
  • Webhooks: Receive real-time notifications about hotspot events
  • Data exports: Bulk access to anonymized coverage statistics
See the API Reference for details.

​
Next Steps

System Architecture

Detailed technical architecture

Data Flow

How data moves through the system