> For the complete documentation index, see [llms.txt](https://airouterprotocol.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://airouterprotocol.gitbook.io/whitepaper/protocol-architecture/overview.md).

# Overview

<figure><img src="https://1640383613-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FikmP30ueNFl1f4xaKXqB%2Fuploads%2Fh3800N2QGg95jvNJEBRv%2Fimage.png?alt=media&amp;token=f5b16c98-eb92-49cb-b3a4-d5d80a660802" alt=""><figcaption></figcaption></figure>

AIRouter is designed to function without centralized servers or middlemen. The communication pathway is composed of several distinct stages:

#### 1. Node Registration

Nodes register through a smart contract deployed on Sui. Registration requires staking $AIR tokens to ensure honest participation. Each node is assigned a reputation score based on uptime and delivery quality.

#### 2. Message Initialization

When a dApp or device wants to send data, it initiates a connection to the nearest available node. Proximity is measured by latency and bandwidth availability.

#### 3. Routing Logic

Once received, the message is encrypted and passed through a routing algorithm that considers path quality, current traffic conditions, and node trustworthiness. Nodes are rewarded for efficiently forwarding packets.

#### 4. Delivery and Confirmation

At the receiving end, the final node decrypts and verifies the data payload using on-chain proofs. Confirmation receipts can be optionally sent back to the sender for high-assurance scenarios.

#### 5. On-Chain Activity Logging

Each transaction, whether it’s message routing, node uptime report, or fee collection, is recorded on Sui’s blockchain. This makes all communication auditable without exposing message content.