> For the complete documentation index, see [llms.txt](https://aetherservice.gitbook.io/about/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aetherservice.gitbook.io/about/trust-scalability-and-execution-strategy/multi-platform-infrastructure.md). # Multi-Platform Infrastructure Aether is initially developed as a cross-platform distributed bandwidth system where each operating system functions as an equal participant node within the network. However, each platform introduces its own constraints in terms of system architecture, power consumption models, network stack behavior, and background execution policies. For this reason, Aether is designed to integrate natively with each operating system while preserving consistent behavior across the **Bandwidth Layer** and the **Reward Layer**. ### Desktop Systems On macOS, the Aether client operates on top of the **Network Extension Framework**, enabling the creation of a secure transport tunnel while remaining compliant with system-level policies. The implementation leverages low-level networking interfaces aligned with the Darwin kernel architecture, reducing latency in bandwidth allocation and improving resource distribution under constrained system conditions. Special optimization is applied for energy efficiency: when a device switches to battery mode, the client automatically reduces network priority while maintaining continuous participation in the bandwidth contribution system without degrading user experience. On Windows, the client integrates more deeply with the operating system network stack through **WinTUN** and a custom abstraction over the **Windows Filtering Platform (WFP)**. This enables higher throughput performance and greater parallelism in connection handling compared to other platforms. The architecture separates execution into independent processes for **Data Relay**, **Telemetry**, and **Reward Calculation**, improving fault tolerance and enabling modular updates without requiring full application restarts. ### Mobile Devices Mobile platforms represent the scalability layer of the network, providing extreme geographic distribution and high device density. Aether is designed to operate within strict mobile OS constraints while maintaining meaningful bandwidth contribution across both Android and iOS ecosystems. On Android, the system utilizes **VpnService** combined with an adaptive transport engine that dynamically adjusts bandwidth usage based on battery state, network conditions, background execution limitations, and power-saving configurations. The system intelligently switches between Wi-Fi and cellular networks (LTE/5G), and restricts mobile data usage unless explicitly authorized by the user. The Android client supports burst-based contribution models, allowing short, high-intensity participation intervals that accumulate into significant aggregate bandwidth without requiring persistent background execution. On iOS, Aether is implemented using the **Network Extension framework** and **NEPacketTunnelProvider**, operating within a highly restricted execution environment defined by system policies. The architecture is optimized around two core mechanisms: **packet batching**, which minimizes system wake cycles, and **contextual sessions**, where the device contributes bandwidth during defined operational windows. This allows iOS devices to participate effectively in the network while respecting strict background execution limits and maintaining low battery impact. ### Unified Capsule Scheme All platforms are unified under a single **encapsulation and transport model**, enabling desktops and mobile devices to operate as compatible nodes within the same network topology. Despite differences in system-level implementation, all traffic is normalized into a shared format for **Proof-of-Bandwidth verification**, **reward computation**, and **session validation**, ensuring consistency across the entire ecosystem. ### Resulting Network Structure The result is a heterogeneous but unified infrastructure where each device category contributes a distinct functional role: Windows systems provide maximum computational throughput, macOS devices ensure stability and energy efficiency, Android devices enable large-scale geographic distribution and flexibility, and iOS devices contribute high-value, controlled participation sessions. Together, these systems form a **resilient, multi-platform decentralized network**, where any connected device — from high-performance workstations to mobile phones — functions as a fully integrated node within the Aether ecosystem. --- # 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: ``` GET https://aetherservice.gitbook.io/about/trust-scalability-and-execution-strategy/multi-platform-infrastructure.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.