Consumer session

Consumer Session Flow (with Proof of Demand)

1. Session Request to Matchmaking Service

   • The consumer node sends a session request to the Matchmaking service.

   • Request metadata includes:

     • Target region

     • Required bandwidth or QoS

     • Session budget

     • Consumer ID

2. Add to Consumer Pool

   • Matchmaking service:

     • Adds the consumer to the pending consumer pool

     • Stores request data with TTL (e.g., 60 seconds)

     • Flags request as awaiting provider match

3. Latency Check with Candidate Providers

   • The system scans the provider pool for matching candidates.

   • Candidate providers are pinged from the consumer or via relay nodes to:

     • Measure round-trip time (RTT)

     • Validate real-time reachability and responsiveness

   • Only providers below a latency threshold and with sufficient bandwidth are retained.

4. Provider Selection

   • A provider is selected based on:

     • Latency score

     • Available bandwidth

     • Reputation score and pricing tier

   • The chosen provider’s info is returned to the consumer for handshake.

5. Proof of Demand Submission

   • Before handshake, the consumer:

     • Signs the session request metadata

     • Sends this signed payload as a Proof of Demand to validator nodes

   • Validators:

     • Verify the signature

     • Log the demand event

     • Optionally use this data for auditing, incentives, or anti-spam filters

6. Handshake Initiation

   • The consumer initiates a direct handshake with the selected provider.

   • Negotiates secure session tunnel

   • Establishes auxiliary reporting channels

7. Connection Established

   • Encrypted traffic begins to flow directly between consumer and provider.

   • Real-time session metrics are pushed to validators for tracking and eventual settlement