> For the complete documentation index, see [llms.txt](https://aethernetwork.gitbook.io/aethernetwork-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aethernetwork.gitbook.io/aethernetwork-docs/advance/architecture.md). # Architecture Aether is built on a modular architecture where each component solves a specific foundational problem in Web3, and all components combine to form a complete decentralized operating stack. Instead of building a monolithic chain that tries to solve everything at once, Aether is engineered as a set of interoperable primitives — each independently upgradeable, independently usable, and collectively powerful when used together. At the base layer is **Aether Vault**, which secures user assets through non-custodial access control and programmable security policies. Vault ensures that ownership never leaves the user — assets remain in self-custody while still supporting institutional-grade governance models, multi-factor approvals, and auditable transaction permissions. Vault replaces custodial storage and centralized risk with cryptographic access enforcement. **Aether Bridge** is the movement layer. It enables secure transfer of assets and data across chains using cryptographic proof validation. Traditional bridges rely on centralized signers or wrapped synthetic assets — both single points of failure. Aether Bridge removes these risks and turns blockchain networks into interoperable execution environments instead of isolated silos, enabling a unified cross-chain economy. **Aether Identity** is the trust layer. It allows users to verify facts about themselves — compliance status, eligibility, age, residency — without exposing personal data. Using selective disclosure zero-knowledge proofs, Identity separates verification from data exposure. This brings privacy and compliance into harmony, enabling regulated markets without sacrificing user sovereignty. **Aether Pay** is the settlement layer. Payments in Aether are not manual transfers — they are programmable outcomes. Pay supports cross-chain settlement, streamed value flows, subscription-style payments, and conditional automated payments triggered by smart contract logic. This turns settlement into a native function of the protocol, not an external service. Taken together, Vault secures assets, Bridge moves assets, Identity verifies trust, and Pay settles value. These modules combine into a fully composable infrastructure layer that any application, protocol, or enterprise can integrate. Aether modularity is what enables true decentralization: each component removes one of the biggest centralized dependencies in Web3 — and collectively, they eliminate the need for centralized intermediaries entirely. --- # 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://aethernetwork.gitbook.io/aethernetwork-docs/advance/architecture.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.