> For the complete documentation index, see [llms.txt](https://docs.metaid.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metaid.io/zh-hk/gai-yao/shu-yu.md).

# 術語

在本MetaID 文檔裏,我們引入了一些新術語:

### MetaID

MetaID 定義為用戶數據樹的根部索引值。該值為全局唯一。MetaID 協議本質就是生成這個用戶數據樹的一套約定。本文檔中,MetaID有時既指這個索引值,有時也會將 MetaID 協議和相關方法簡稱為 MetaID。

#### 生成規則

MetaID的生成規則基於將用戶的 Address 通過SHA256哈希處理得到,因此 Address 就自帶有唯一的 MetaID。

```jsx
MetaID=SHA256(Address)
```

#### MetaID樹

符合 MetaID 規則而生成的樹狀數據結構，我們稱為"MetaID 樹"。MetaID 樹是通過用戶自己 PIN 中的path,構建出一個相互關聯、有向無環的樹狀數據結構,詳見"MetaID樹介紹"詞條。

### PIN

PIN是指Personal Information Node，在 MetaID 樹上每一個節點和葉子都是一個 PIN。簡單來說每一條在鏈上銘刻的 MetaID 數據都稱為 PIN,詳見"關於 PIN"詞條。

### PoP

PoP是指 Proof of PIN，它和隨機性以及該 PIN 所在區塊的算力難度相關，用於反映用戶 MetaID 數據的價值和用戶在MetaID 世界中的"工作量"，詳見"關於PoP"詞條。

### MAN

MAN 是指 MetaID App Node，是第一個遵循 MetaID V2 協議的後端索引器，目標是打造基於 MetaID 的分佈式存儲節點，以及方便開發者可以在不依賴第三方服務商開發去中心化的 MetaID 應用。詳見"MAN"部分相關文檔。


---

# 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://docs.metaid.io/zh-hk/gai-yao/shu-yu.md?ask=<question>&goal=<endgoal>
```

`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.