This document explains how bandwidth sharing works within the Upproret network — what gets shared, what never does, how privacy is preserved, and how compensation is calculated.
When your bridge agent is active, it routes anonymized data relay traffic through your connection. This traffic is exclusively composed of encrypted payloads — no plaintext content ever traverses your node. Specifically, the bridge handles:
The following traffic categories are permanently excluded and cannot be enabled by any partner or configuration:
Upproret operates on a zero-knowledge relay model. Your node receives and forwards encrypted payloads — you cannot inspect the contents and neither can we. The encryption keys are held exclusively by the originating partner and the destination endpoint.
Your IP address is never exposed to traffic destinations. All relay requests are proxied through the Upproret gateway layer, which acts as the visible egress point. Your participation is not logged in any externally accessible ledger.
Compensation is based on verified throughput — the actual volume of relay traffic successfully processed by your node each calendar month. Rates are denominated in USD per GB and vary by traffic category and time-of-day demand.
The bridge agent is a lightweight daemon that runs on your device and connects to the Upproret gateway over an encrypted tunnel (TLS 1.3, minimum). It enforces your configured bandwidth cap at the kernel level and suspends automatically when your device's primary use exceeds a configurable CPU or network threshold.
The agent is open source. Every line of code is auditable. It requests only the permissions it needs: network access and the ability to read your configured limits. It does not access your filesystem, installed applications, or any system resources outside network relay.
Stable release — v0.1.0-beta. Read the source before installing.