# MetaID PIN规则约定

#### 关于`modify`/`revoke`

1. `modify`和`revoke`发起者address必须和旧版本的pin的创作者address一致，并且是未发生过转移的pin，若PIN发生过转移，后续的`modify`/`revoke`为无效。`path`为`/info`下的PIN仅需发起者address和旧版本的pin的创作者address一致即可修改。
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/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.