> For the complete documentation index, see [llms.txt](https://airshipx.gitbook.io/airshipx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://airshipx.gitbook.io/airshipx/airshipx-witherpaper/chapter-4-airshipxsystem-architecture/4.1-basic-architecture-logic.md).

# 4.1 Basic Architecture Logic

The system architecture of AirshipX platform can be simply divided into three layers, protocol layer, extension layer and application layer. Among them, the protocol layer can be divided into storage layer and network layer, which are independent but inseparable. As shown：

<figure><img src="/files/aTF8wSHhxc7fMe7xN1iH" alt=""><figcaption><p>AirshipX infrastructure</p></figcaption></figure>

The protocol layer refers to the most underlying technology. It mainly includes four aspects: network programming, distributed algorithm, encrypted signature, and data storage technology. The principles of data storage selection are performance and ease of use. Distributed algorithms, encrypted signatures must be used in the process of implementing peer-to-peer networks.

The extension layer is to make blockchain products more practical. This project is an expansion for communication, and "smart contract" is a typical application development at the expansion layer. The so-called "smart contract" is "programmable contract", or "intelligent contract", in which "intelligence" is the intelligence in execution, that is to say, when a certain condition is reached, the contract is automatically executed, such as automatic trade, automatic payment, etc. . Technologies used in the extension layer include distributed storage, machine learning, VR, business collaboration, big data, and more.

The application layer is a product that people can really use directly, and it can also be understood as the browser side (Browser) in a product with a B/S architecture.


---

# 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://airshipx.gitbook.io/airshipx/airshipx-witherpaper/chapter-4-airshipxsystem-architecture/4.1-basic-architecture-logic.md?ask=<question>
```

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.