U2DPN Documentation
  • Introduction
  • High level architecture
    • Provider session
    • Consumer session
    • Data transfer
  • Assets and features
    • Tokens
    • Reputation System
    • Bidding
    • Referral
  • User guide
    • Best practices
    • Common issues
  • Glossaries
  • Privacy Policy
Powered by GitBook
On this page
  1. High level architecture

Data transfer

Handshake & Data Transfer Phase

PreviousConsumer sessionNextAssets and features

Last updated 2 days ago

1. Peer-to-Peer Handshake

  • The consumer initiates a secure session with the selected provider node.

  • A transport-level handshake is performed using protocols such as WireGuard, QUIC, or TLS.

  • During the handshake, both parties negotiate transport parameters including encryption keys, compression settings, and timeout policies.

2. Auxiliary Reporting Channel Setup

  • Once the tunnel is established:

    • Side channels are opened from both consumer and provider to a set of validator nodes.

    • These channels are used to stream real-time metadata, including session ID, timestamps, and traffic stats.

    • This enables independent verification of session integrity and performance.

3. Encrypted Data Transfer

  • Encrypted traffic begins flowing from the consumer through the provider.

  • Traffic includes application-level payloads routed via the provider’s node.

  • The system actively monitors Quality of Service (QoS) metrics such as:

    • Latency (RTT)

    • Throughput (bandwidth delivered)

    • Packet loss or jitter, if relevant to QoS guarantees

4. Continuous Session Monitoring

  • Validator nodes receive and analyze real-time session reports.

  • They verify key metrics including:

    • Session duration

    • Total bandwidth consumed

    • Liveness and availability of both parties

  • Any anomalies (e.g., dropped connections, under-delivery) are logged for later dispute resolution.

5. Session Termination

  • When the session ends (either by disconnect or timeout):

    • Both provider and consumer submit final session proofs to the validator nodes.

    • Proofs include final usage statistics and signed timestamps.

    • Validators cross-check reports for consistency.

6. Settlement & Reward Distribution

  • Upon successful verification:

    • Smart contracts calculate and disburse token rewards to the provider based on verified traffic.

    • The consumer is charged based on the agreed demand parameters and actual service delivered.

    • All transactions are recorded on-chain to ensure transparency and auditability.