Masternode setup on Windows with 1 wallet
Last updated
Was this helpful?
Last updated
Was this helpful?
TWINS Masternodes system has now introduced a multi-tier level structure. It exists of four tiers: 1M (one million) TWINS, 5M TWINS, 20M TWINS and 100M TWINS (Supernode). While this guide will use 1M collateral as an example, the only difference in setting up the masternode tiers are the amount of coins to be send to an address and locked.
In the article we describe how to set up a masternode on Windows with 2 wallets. In this manual we will use only one TWINS wallet to set up a masternode on Windows.
First of all, we need to explain the downsides and limitations of using one wallet for two purposes. Here we use one TWINS wallet as a remote wallet and as a local wallet at the same time. We call a wallet local if we store our TWINS coins in it, use it to send and receive payments, and stake. We call a wallet a remote wallet if it is empty, blank and only has one purpose – to be always online with a static IP address and store the masternode private key.
When we use a wallet for both purposes, as a local and remote wallet in one place, this poses a security risk because your wallet is always online with a known masternode IP address. Somebody can use this information to gain access to your TWINS wallet and coins. The single IP address in use is also a limitation factor because you will only be able to start one copy of the same wallet. If you know that you don't have additional hardware and won’t plan to start more than one masternode, this option makes sense. A masternode requires the wallet to be always on and stay connected, in order to support the network and receive rewards. Because of this the wallet can also be used for staking at the same time without interruption.
Now we will explain the configuration files. All main local wallet settings can be found in the masternode.conf file. Remote wallet settings are in the twins.conf file.
So, let’s start. We won’t cover the TWINS wallet setup process because it is described in the following article: . We presume that you already have a TWINS wallet installed on your PC or laptop.
To start, we need a masternode private key. We have to generate it. Let’s open our local wallet and go to Tools > Debug console. In the console type the text
masternode genkey
Copy the result somewhere - in Notepad for example. It will look something like 93HaYBVUCYjEMeeH1Y4sBGLALQZE1Yc1K64xiqgX37tGBDQL8Xg (Image 1).
Now you have to enter the lines below Image 2 into the configuration file twins.conf. You can access it directly in the folder where your wallet is installed, or click Tools > Open Wallet Configuration Files (Image 2). If you see a system request regarding which program you want to open it with, you can choose Notepad again.
You have to write (or paste) the following information inside:
rpcuser=LongRandomUsername
rpcpassword=LongerRandomPassword
rpcallowip=127.0.0.1
server=1
daemon=1
logtimestamps=1
maxconnections=256
masternode=1
externalip=31.32.33.34
port=37817
masternodeprivkey=93HaYBVUCYjEMeeH1Y4sBGLALQZE1Yc1K64xiqgX37tGBDQL8Xg
After you have finished editing the twins.conf file and saved it, close the TWINS wallet and start it again. All necessary changes will have been integrated.
getaccountaddress ChooseAnyNameForYourMasternode
Now that you have the address ready you can send the 1,000,000 TWINS collateral to it.
Wait until the first confirmation for the transaction output to be visible in the console. Go to Tools > Debug Console to find out the TXID. Type the command:
masternode outputs
Two fields similar to Image 3 will come up - txhash and outputidx. The results from those will be entered into the masternode.conf file.
Open the masternode.conf file directly in the wallet folder or via Tools > Open the Masternode Configuration File and fill it in like in the example below:
<MN alias> <unique IP address>:37817 <your MN private key> <transaction ID (txhash)> <output index 0 or 1 (outputidx)>. Also see the example of Image 4.
Save and close the conf file and restart your wallet. Wait for the MN collateral transaction to receive 16 confirmations before starting the masternode.
Go to the Masternodes tab. The new MN should be present with an alias, IP address and the MISSING status, which indicates the masternode has not been started yet.
In the Transactions tab you can check whether the MN transaction has received at least 16 confirmations. If it has, go back to the Masternodes tab to start the masternode. Right-click on the MN and do Start alias (Image 5). The MISSING status will have changed to ENABLED and your masternode has started. Good job!
Now you want to double-check the MN status. Open the console via Tools > Debug console and type
masternode status
The latest status will come up with the message Masternode successfully started, similar to Image 6.
The first MN reward The average time it takes to receive the first reward is calculated in hours with the formula millions_locked_before_your_MN_is_enabled*2.6/60. At the time of writing the total number of millions that are locked in MNs is 3,500 million, so 3500*2.6/60=151.67 hours or approximately 6 days, 7 hours and 40 minutes.
You need to send exactly 1 million TWINS (1,000,000) to any of your wallet addresses. For better clarity you can name this address during the creation process. How to do this is described in the manual Using the wallet - , or just run the following command via Tools > Debug Console to create a new adress with a suitable name (e.g. MN)
For good practice it is best to also check the status on the TWINS explorer website - - and find your masternode via the search bar. Your MN status here will be set as Active.
*NOTE: if the masternode status is set as MISSING in your local wallet, always check its status in the masternode explorer - . It might be showing EXPIRED or REMOVED there during the starting process which is correct. It is always better to double-check the status with the community rather than hastily do Start alias again!
