> For the complete documentation index, see [llms.txt](https://docs.iotex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iotex.io/ioid/technical-specification/system-architecture.md).

# System Architecture

## System Architecture

A high-level system architecture of ioID is illustrated in the figure below.

<figure><img src="https://content.gitbook.com/content/SgFhJ0QnECVPLM1rnhhd/blobs/4P7S9emtQdgDR57iEwMa/Screenshot%202025-05-20%20at%2012.07.40%E2%80%AFPM.png" alt=""><figcaption><p>A High-Level Architecture of ioID</p></figcaption></figure>

### Components of ioID

ioID consists of the following core components:

**Decentralized Identifier**\
A globally unique, W3C-compliant [decentralized identifier](https://www.w3.org/TR/did-1.0/) used to represent the identity of a machine or agent in a portable and verifiable way.

**Device NFT**\
A digital representation of a physical or virtual device on-chain, implemented as an [ERC-721](https://eips.ethereum.org/EIPS/eip-721) token. This NFT is typically minted by a DePIN (Decentralized Physical Infrastructure Network) project and serves as the anchor for identity and ownership.

**Machine-Bound Account (MBA)**\
A smart contract wallet inspired by [ERC-6551](https://eips.ethereum.org/EIPS/eip-6551), created for each device NFT. The MBA enables the machine to interact directly with decentralized applications (dApps), manage assets, and execute transactions autonomously.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.iotex.io/ioid/technical-specification/system-architecture.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.