> For the complete documentation index, see [llms.txt](https://delegates.iotex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://delegates.iotex.io/get-started/profile-registration/name-registration.md).

# Name Registration

The Name Registration is the most crucial part of the registration process: on this page, you can set the unique name that identifies your delegate node in the network. 

Later on you will configure the staking requirements for your delegate and the rewards mechanism.

<figure><img src="https://1634134081-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5whGkGlpM5BFduENPztv%2Fuploads%2FNsIaWZDFXU9EDsZ83Ix7%2FScreen%20Shot%202022-09-15%20at%209.36.54%20AM.png?alt=media&amp;token=92d42871-0f9e-49a2-af6f-ec85d047f635" alt=""><figcaption></figcaption></figure>

### Profile Account Name

The Profile Account Name is a 12 alphanumeric characters string and is used to uniquely identify the delgates in the network.&#x20;

### Delegate Name

The Delegate Name is your user-friendly public facing name, and is a maximum of 20 characters long.&#x20;

### Delegate Bio

Use a sentence that represents your Delegate brand.&#x20;

### Operator Address

This account is used for the actual node software running on your node servers and we therefore recommend using a different address than the one used in the Profile Account, since if it would get somehow compromised, delegates will forever lose access.&#x20;

### Email Address

Make sure to add a reliable email address, possibly one  that connects directly to the node operator, as IoTeX will use this email address to send update notifications to delegate operators as well as other urgent communications.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://delegates.iotex.io/get-started/profile-registration/name-registration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.