> 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/blockchain-development/commands.md).

# Commands

These are commands we introduce periodically in each wallet update

* **`checkconnection`** RPC call: This call allows you to test the connectivity of your server with other nodes on the network.<br>
* **`mnping`** RPC call\`: This call allows you to send a ping message to your masternode and receive a pong response. It helps you verify that your masternode is online and responsive.<br>
* **`reloadmasternodeconfig`** RPC call and a corresponding GUI element: This call and element allow you to reload your masternode configuration file from the command line or the user interface. It is useful if you want to make changes to your masternode settings without stopping or restarting them.<br>
* **`setautocombinethreshold`** command and UI support: This command replaces the deprecated `autocombinerewards` command, which automatically combines small inputs into larger ones to reduce transaction fees and improve privacy. The new command allows you to set a threshold amount for auto-combining inputs and enable or disable this feature from the command line or the user interface.<br>
* **`rewindblockindex`** command, start option, and the GUI element: This command allows you to rewind your block index in case of a fork or a corrupted database. It deletes all blocks after a specified height and re-syncs with the network from that point. It can help you recover from various issues that may affect your wallet functionality or integrity.<br>
* **`getactivemasternodecount`** RPC/CLI command: The command reports the number of active masternodes of a wallet.


---

# 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/blockchain-development/commands.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.