# Info Node

### **Info Node Overview**

The Info node is specifically designed to store users' personal information. Through the Info node, users can securely store and manage their personal information on the blockchain.

### **Basic Information about the Info Node**

The protocol stipulates that the Info node must include the following five sub-nodes:

* **name**: User name, recommended not to be encrypted. The format is fixed as text/plain.
* **avatar**: User image, recommended not to be encrypted. The format is binary, with the payload part storing the image's binary stream.
* **bio**: User personal bio, recommended not to be encrypted. The format is fixed as text/plain.

### **Data Format**

The personal information of users is stored in the following format:

```c
OP_FALSE
OP_IF
   metaid                
   create                
   /info/name            
   0                    
   OP_0                
   text/plain           
   Alice                 // Example user name
OP_ENDIF
```

### **Info Node Path**

The path for the Info node uses **`/info`** as the base path and distinguishes different types of personal information through subsequent paths. For example, **`/info/name`** can be used to store the user's name, while **`/info/avatar`** can be used to store the user's avatar information. By storing personal information under different type paths, users can clearly organize and manage their personal profiles.

If the application needs to add user information, it can add child nodes after the **`/info`** node. For example, **`/info/email`** represents the user's email information.

<br>


---

# 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/metaid-specification/metaid-tree/info-node.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.