# MetaID PIN規則約定

#### 關於`modify`/`revoke`

1. `modify`和`revoke`的發起者地址必須與舊版本PIN的創建者地址一致，並且是未發生過轉移的PIN。如果PIN發生過轉移，後續的`modify`/`revoke`將無效。`path`為`/info`下的PIN僅需發起者地址和舊版本的PIN的創建者地址一致即可修改。
2. 所修改的PIN必須是當前最新版本的PIN才有效，即如果所修改的PIN不是當前最新版本的PIN，所有的`modify`/`revoke`將無效。
3. 被修改的PIN和新修改的PIN需要被打包在不同的塊高才有效，如果被修改的PIN和新修改的PIN被打包在同一個區塊，新修改的PIN將無效。
4. 當`operation`為`modify`/`revoke`時，`path`需要指向對應的PIN，例如：`@{pinid}`。所指向的PIN必須是用戶已在鏈上存在並打包出塊的PIN的`path`，才是有效的`modify`/`revoke`，所針對的PIN必須在不同的塊高。

<figure><img src="/files/vuAEwTLHgx91i0U6IgYL" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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://docs.metaid.io/zh-hk/metaid-app-node/metaid-pin-gui-ze-yue-ding.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.