> For the complete documentation index, see [llms.txt](https://docs.decenomy.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decenomy.net/tutorials/decenomy-multinode-script/coin-selection/masternode-multinode-management.md).

# Masternode multinode management

Script option detailed

<figure><img src="https://505947675-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MiHm486VotxVq44a_Jg%2Fuploads%2FQCWimv2H5LzHHy1ntYPt%2FScript_4_masternode_multinode_management.png?alt=media&amp;token=b2f71612-de38-499c-9a69-ba744061d21b" alt=""><figcaption></figcaption></figure>

One place to manage everything related to multinode.

### \[1] - List of masternodes in multinode List

This section lists all the multinodes already installed in the system, taking into account the previously selected coin.

<div align="left"><figure><img src="https://505947675-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MiHm486VotxVq44a_Jg%2Fuploads%2FBHGbuSHJZgfUmWikNhUy%2FScript_4_1_List_of_masternodes_in_multinode_List.PNG?alt=media&amp;token=9795a4e5-f135-4377-a1df-d5b023536907" alt=""><figcaption></figcaption></figure></div>

The multinode result is always sorted by the alias and then by the masternodeKey.

### \[2] - Add masternode to multinode List

This option allows you to add new multinode configurations and view those that have already been created or are currently being created.

<div align="left"><figure><img src="https://505947675-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MiHm486VotxVq44a_Jg%2Fuploads%2FkY9E3GHs4haNaKvi5XD3%2FScript_4_2_Add_masternode_to_multinode_List.png?alt=media&amp;token=e7eff646-8725-47d9-a5cc-948dc1e008d9" alt=""><figcaption></figcaption></figure></div>

#### **Section 1**

It displays the same information as the previous option for listing multinodes.

#### **Section 2**

This is a guide to help you easily understand how to fill out the multinode file.

#### **Section 3**

The multinode information must be entered in steps. \
First, the alias is requested, and then only the masternodeKey is requested. In this last step, the key can be entered manually or generated automatically by pressing the Enter key.

<div align="left"><figure><img src="https://505947675-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MiHm486VotxVq44a_Jg%2Fuploads%2FMc8xSYreCiLEKZYcXgBl%2FScript_4_3_Add_masternode_to_multinode_List.PNG?alt=media&amp;token=4a53dfb7-fd67-4d1e-9c78-8882cd740737" alt=""><figcaption></figcaption></figure></div>

This screen also shows the previously introduced alias as a reference.

### \[3] - Delete masternodes from multinode list

This is an easy way to delete previously introduced multinode information.

<div align="left"><figure><img src="https://505947675-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MiHm486VotxVq44a_Jg%2Fuploads%2F8YdS8JXwr2Pibf2suYwb%2FScript_4_4_Delete_masternode_from_multinode_List.PNG?alt=media&amp;token=6366b44c-db46-4aaa-a8aa-45cf0ab7c3d6" alt=""><figcaption></figcaption></figure></div>

Each line is numbered, making it easier to select the exact information to be deleted. After the selection is made, a confirmation screen is displayed and upon confirmation, the screen is updated with the final information.


---

# 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://docs.decenomy.net/tutorials/decenomy-multinode-script/coin-selection/masternode-multinode-management.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.
