High level architecture
Last updated
Last updated
Provider Registration & Pooling Once a provider successfully registers and connects to the U2DPN subnet, it is added to the active connection pool managed by the network.
Consumer Request via DNS Resolver A consumer initiates a request through the DNS Resolver, including metadata that describes their bandwidth or service demand. This request is broadcast across the subnet to locate the most suitable provider based on availability, performance, and policy.
Session Establishment Once a match is found, the consumer and provider perform a handshake to establish a Private Channel for bandwidth sharing. Simultaneously, they open a Reporting Channel to track:
Bandwidth usage
Session duration
Fees incurred These metrics are sent to the DPN Master Node.
Session Verification & Proof Recording The DPN Master Node continuously verifies session integrity and stores cryptographic proofs until the session ends.
Reward Calculation & Distribution Based on verified metrics and total bandwidth contributed, the DPN Master Node calculates the provider’s reward. Consumers may claim any eligible incentives or credits after the session closes.
Indexing Protocol The Indexing Protocol catalogs all sessions and subnets in the U2DPN network. It performs post-processing and presents session data in a human-readable format (e.g., dashboards, explorer UIs).
Messaging Protocol A Messaging Protocol is responsible for broadcasting session updates, alerts, and profile changes to providers in real time.
