> 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/introduction/delegate-requirements.md). # Delegate Requirements Being a decentralized network, IoTeX allows **anyone** to register and become a **Delegate** at any time. However, all Delegates must meet some minimum requirements. These minimum Delegate Requirements are summarized below and will be addressed in detail in the next sections: ### **Delegate Profile** Every Delegate must have its *identity* registered on the IoTeX blockchain, in the form of a blockchain account. This identity is called the *Profile Account* of the Delegate. ### **Self-Staked IOTX** To become eligible, the Delegate profile account must self-stake at least 1,200,000 IOTX. [IoTeX Delegate Sponsorship Program → ](/get-started/delegate-endorsement/delegate-sponsorship-program.md) ### **Delegated Votes** Once the Delegate is eligible, the profile account must receive at least 2,000,000 total votes. ### Technical requirements Technical requirements are not mandatory, but it's highly recommended that your infrastructure meets at least the minimum requirements as listed in the [Operational Costs](/introduction/hardware-specs.md) section. --- # 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/introduction/delegate-requirements.md?ask=&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.