> 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/metaid-app-node/metaid-pin-conventions.md).

# MetaID PIN Conventions

#### About `modify`/`revoke`

1. The address initiating the `modify` or `revoke` must match the address of the creator of the old version of the PIN, and the PIN must not have been transferred. If the PIN has been transferred, any subsequent `modify`/`revoke` operations will be invalid. For PINs under the `/info` path, only the initiator's address and the address of the creator of the old version of the PIN need to match for modification.
2. The PIN being modified must be the current latest version of the PIN for the modification to be valid. If the PIN being modified is not the current latest version, all `modify`/`revoke` operations will be invalid.
3. The modified PIN and the newly modified PIN need to be packaged in different block heights to be valid. If the modified PIN and the newly modified PIN are packaged in the same block, the new modification will be invalid.
4. When the `operation` is `modify`/`revoke`, the `path` needs to point to the corresponding PIN, for example: `@{pinid}`. The pointed PIN must be a PIN that exists on the chain and has been packaged into a block for the `modify`/`revoke` to be valid. The targeted PIN must be in different block heights.

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


---

# 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/metaid-app-node/metaid-pin-conventions.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.