> For the complete documentation index, see [llms.txt](https://xnet-mobile.gitbook.io/xnet-mobile-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xnet-mobile.gitbook.io/xnet-mobile-docs/deploy-connect-earn/how-xnet-works.md). # How XNET Works **Carrier Value Proposition: Lower Costs, Happier Customers** XNET offers carriers a compelling **zero-CapEx solution** to rapidly extend their network coverage and capacity. By utilizing existing decentralized Wi-Fi infrastructure maintained by XNET operators, carriers avoid costly infrastructure investments typically associated with traditional 5G network expansion. Offloading cellular data onto XNET’s neutral-host network significantly reduces operational costs associated manufacturing and delivering data to their subscribers. This directly improves connection speeds, enhances network reliability, and boosts overall satisfaction—key drivers in reducing subscriber churn and increasing customer loyalty. **Network Architecture:** * Enterprise and Carrier-grade Wi-Fi access points form the network backbone * Automatic authentication through carrier certificates * Real-time traffic management and load balancing * Distributed network design for optimal coverage **Data Flow Process:** 1. Mobile device enters XNET coverage area 2. Device authenticates automatically via Hotspot 2.0 3. Traffic transitions from cellular to Wi-Fi network 4. Data usage is recorded and verified 5. Token rewards are distributed to AP owners **Requirements:** * XNET approved WiFi 6/6E/7 Passpoints * Consistent uninterrupted backhaul (min. 100 Mbps down, min. 10 Mbps up) * "Carrier Approved" Business, commercial and public locations **Security Measures:** * Carrier-grade WPA2/3 encryption for all traffic * Network isolation prevents device-to-device visibility * Compliance with all mandated telecommunications standards ### **Data Offloading Process** * **Seamless Connection**: Utilizing Hotspot 2.0 technology, mobile devices automatically and securely connect to XNET hotspots without passwords, manual logins, credentials or additional apps. * **Carrier Integration**: Mobile Network Operators (MNOs) and Mobile Virtual Network Operators (MVNOs) integrate with XNET through standardized roaming agreements. This integration allows carriers to efficiently divert traffic to XNET's network in areas of high demand or limited coverage. * **Reduced Congestion**: Offloading cellular data helps carriers reduce network congestion, especially in densely populated or event-driven environments (stadiums, transportation centers, urban centers). ### **Rewarding Network Participants** Participants (Deployers, MSPs, ISPs) are rewarded in $XNET tokens based on their contribution: * **Data Throughput**: Rewards scale with the amount of data offloaded through their deployed hardware. More Data = More Rewards * **Proof-of-Coverage:** To ensure network growth XNET also employs a Proof-of-Coverage (PoC) mechanism. * **Strategic Placement**: Hotspots deployed in carrier marked, high-density and high-usage areas have the potential to earn substantially more, incentivizing rapid network growth in valued locations. {% embed url="" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://xnet-mobile.gitbook.io/xnet-mobile-docs/deploy-connect-earn/how-xnet-works.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.