Provider session

Provider Registration & Heartbeat Flow

1. Initial Ping to DNS Resolver

   • The provider node sends a ping request to the DNS resolver announcing its presence.

   • Request payload includes:

     • Public IP address

     • Available bandwidth

     • Geolocation (optional)

     • Unique provider ID (e.g., public key or UUID)

2. Add to Provider Pool

   • The DNS resolver:

     • Inserts the provider into the active provider pool

     • Stores all relevant network metadata

     • Marks status as pending_verification

3. Latency Checks

   • The DNS resolver (or an orchestrator node):

     • Sends test packets to all available master nodes from the provider

     • Measures round-trip latency (RTT) for each

     • Stores latency metrics for optimized session routing

4. Connection Confirmation

   • If latency checks succeed:

     • The provider is marked as connected

     • Its session becomes available for client matchmaking

5. Heartbeat Mechanism (Every 30 Seconds)

   • Provider sends regular ping messages to the DNS resolver to:

     • Refresh its presence in the pool

     • Update metadata (bandwidth, IP, etc.)

     • Prevent expiration (e.g., TTL = 90 seconds)

6. Send Proof to Validator Nodes

   • With each successful heartbeat, or periodically (e.g., every N intervals):

     • The provider sends a proof payload to validator nodes

     • Proof includes:

       • Recent activity logs

       • Session stats (uptime, bandwidth served, IP consistency)

       • Cryptographic signature to ensure authenticity

   • Validators verify and archive proofs for reward settlement or reputation scoring