> 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/flits-wallet-app/how-to-deploy-masternodes-in-the-flits-wallet-app.md).
# How to Deploy Masternodes in the Flits Wallet App
This guide takes you through the process of setting up a masternode inside the Flits Wallet App
### Step 1
* Select '**Wallets**' while on the home page
* Next, we choose FLS because that's the coin we want to deploy a masternode for.
### Step 2
* On the '**Overview**' tab in the FLS wallet, select '**Nodes**' as shown in the image below:
### Step 3
* Click on '**New node**' to start the setup process
### Step 4
* While on the setup page, click on '**Start your masternode**'
### Step 5
* Specify the number of masternodes you would like to deploy. This also depends on your available balance.
* Next, click on '**Deploy masternodes**'
### Step 6
* If everything goes well, you will be sent to the confirmation page, indicating your nodes are being installed.
### Step 7
* Go back to the '**Masternodes**' tab, and you will find your masternode and its initial status.
* After about 30 minutes, the status of your masternode should change to '**Enabled**' as seen in the image below:
---
# 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/flits-wallet-app/how-to-deploy-masternodes-in-the-flits-wallet-app.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.
