> For the complete documentation index, see [llms.txt](https://docs.zeeve.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zeeve.io/validator-nodes/shido/manage-shido-validator-node/edit-validator-details.md). # Edit Validator Details You can change the following details for a validator node: * Validator Name * Commission Rate (%) * Email * Validator Identity * Website * Validator Description Follow these steps to edit the validator's details: **Step 1: Navigate to the Validator Nodes Management Screen** - On the left navigation, click on the [Validator Nodes](https://app.zeeve.io/platform/manage/nodes/validator), where the user can see a list of validator nodes that have been deployed. **Step 2: Navigate to the Detailed page -** Click on the **Manage** button to navigate to the detailed screen of the node, to view these options.

**Step 3: Enter New Value -** Update the desired field and then click on the ***Next*** button to proceed.

**Step 4: Authorize Update -** Now, provide your **Keyring** and click on the ***Update*** button to authorize and initiate the update in the field.

--- # 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.zeeve.io/validator-nodes/shido/manage-shido-validator-node/edit-validator-details.md?ask=&goal= ``` `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.