HOT+COLD Wallet setup Windows & Linux VPS
Also, there are other setup guides out there and they take different approaches and place files in different directories…. jumping between guides is not recommended unless you’re an experienced Linux user and can easily and account for the differences in paths and commands. In such cases we can’t support you! We are this steps from this guide. When you’re doing other, don’t ask about support.
a VPS server with Ubuntu 16.04
installation directory /root
Step 1 - Download and sync the Windows wallet
Step 2 - Setting up the collateral transaction
The first step involves sending exactly the actually needed collateral to a new wallet address. You’ll want to have a small amount above to cover the transaction fee, so you’ll need to have a starting balance of at least, say 10.001.00 GOS. First, we’ll create a new wallet address to hold the collateral. This will also be the address that the masternode rewards are sent to.
In the QT wallet, choose: File->Receiving addresse... and give it a label, such as MN01
Click Request Payment to create the address. You’ll see the new address. Choose Adddress Copy to store that address in the clipboard.
Click Close to exit the receiving address dialog. Now we’ll send the collateral amount to the address you just created.
Under the Send tab, paste the address that you copied into the Pay To: field. The Label field should pre-populate with the label you gave it earlier, in this case, MN01 and in the Amount: field, enter the actual collateral
The actual collateral you will finde here
Click Send and your transaction will be broadcast to the network
You’ll need to wait for 20 confirmations (the current number of confirmations is viewable in the Transactions tab) before the masternode will fully activate. But now wait 1 confirmation before you follow the guide.
We can start working through the rest of the setup in the meantime
All is clear till now? This part was successful? When yes go to the next step, when no start over. All steps are easy and clear. Read, understand and do it.
Step 3 - Generate the masternode private key and txid
Next, we need to access the debug console to output what’s known as the collateral txid and the masternode private key. The collateral txid is an identifier for the transaction of the collateral that you made previously.
The masternode private key is a key that is specific to your wallet and is used to validate your masternode on the network. Like any private key, you want to keep this secret. There’s no reason to share this number with anyone or post it publically.
To access the debug console, go to: Tools->Debug console
In the debug console, type in:
Next, we’ll generate a tx id for you masternode. Type in:
Copy that output and paste it somewhere convenient (in an empty Notepad is fine).
Creating masternode entry in your local wallet. On your local wallet, we need to give it the configuration information for your masternode.
Tools -->Open Masternode Configuration file. This should open up your masternode.conf file in Notepad.
This file has an example line in that can be used as a guide. The # in front of the line indicates that it’s “commented out”, which means it’s effectively ignored. Following this example, we see that the structure is:
alias - a name for your masternode ip address - the IP address for your VPS that is hosting the node masternode private key - the key that we generated previously using masternode genkey txid - the transaction id for your collateral transaction index - the block position of the transaction this is the number that appears at the end of of the txid listed by ‘masternode outputs’
Following this structure, for our example we’re going to add a line that looks like this:
MN01 188.8.131.52:22123 4KKd3zArAHeKn2eoM8NcXeBK78SoALfz3c 20ab6c9920191bf1ef278safsad8e674a5ece7e5b903d9fbf698arqwq 1
NOTE: Between the alias name, IP address, masternode key and tx id is only one blank! Beware that after the last number is no blank!
Double check your entries to make sure they all match up, and then Save and close notepad. Every time you edit or make changes to the masternode.conf file (or any conf file), you need to close and re-open the wallet to initialize the changes.
So close your local wallet, and then re-open. Go to the Masternodes tab and you should see your node listed. Note: For multiple nodes, just add second line after that with the new values.
Step 4 - Setting up a Linux VPS
You will choose a VPS provider which you like. You are paying more than 3$ per month for you server? Be not so lazy and search, you will find nice providers from 1.50$/month. You not need “special” security extras, like DDOS protection.
Use fail2ban and the UFW firewall for security hardening. But what I’m telling you, when you install you’re masternode manually, you know this all.
Be patient with other different masternodes on one server. My suggestion is, run not more than two masternodes on one machine with 1GB memory.
This hardware specs are enough for a stable masternode: 1024 MB (1GB RAM), 20 GB disc, 1 CPU
Step 5 - Logging into your VPS with PuTTY
To access the VPS, we need to use a protocol called SSH. An SSH session will give you command-line access to your VPS and will be the mechanism we use for running commands on the Linux machine. We’ll use a program called PuTTY. (For OSX users, you can use your Terminal and just run the command ssh root@<YOUR VPS IP ADDRESS>)
The latest version of PuTTY can be downloaded from here. Install PuTTY and run it. Once open, you’ll see the standard PuTTy interface: Under Host Name, enter the IP address for your VPS.
You’ll likely see a security alert listing the ssh key fingerprint, choose Yes. Next up, you’ll see the login prompt for your VPS.
Note that in PuTTY, a right-click will paste the contents of your clipboard. So if you’re copying and pasting the root password, a right-click will paste. You won’t see any *’s or feedback for the password when you paste it, so just hit Enter after pasting. If you get an Access Denied message, double-check your root password and try typing it in manually rather than pasting.
Step 6 - Linux Preparation
Update your package repos and update the server with:
apt-get update && apt-get upgrade
Install needed and helpful tools (htop is an performance monitor, fail2ban ssh security, unzip a zip extractor:
apt-get install htop fail2ban unzip nano
When it's done, reboot the machine
After the reboot, you are logged in via putty/ssh to your server
Download the wallet:
Unzip the wallet:
Remove the not needed zip file:
Make the files executable:
chmod +x goss*
Start the daemon to create the needed directories:
Stop the daemon:
Go in the directory .gossipcond:
Download the bootstrap.dat and the peers.dat for a quick sync:
wget https://github.com/g0ssipcoin/bootstrap-peers/releases/download/0.1/bootstrap.zip && wget https://github.com/g0ssipcoin/bootstrap-peers/releases/download/0.1/peers.zip
Edit your config file with the editor of your choice:
Paste the following parameters in this file:
rpcuser=myrpcuser rpcpassword=mylongrandompassword rpcport=22122 rpcallowip=127.0.0.1 listen=1 server=1 daemon=1 port=22123 logintimestamps=1 maxconnections=256 masternode=1 masternodeprivkey=this is the key which you generated in step 2 under (masternode genkey)
Note: When you are using the nano editor, please Press Ctrl+X then Y and enter to save the above information.
All is clear till now? This part was successful? When yes go to the next step, when no start over. All steps are easy and clear. Read, understand and do.
Change the directory one level higher:
Start your| masternode:
Now we must wait for the full synchronization. Check the synced blocks with the actual block count. You can find it in your Windows wallet under Tools --> Information
When you can seethat the blockcount is on the Linux server the same like in the Windows wallet, your server is in sync.
Activate the Masternode. Return to your Windows wallet.
NOTE, before clicking start, make sure your transaction has AT LEAST 20 confirmations, you can check the number of confirmations by hovering the mouse cursor over the transaction in the Transactions tab.
Go to the Masternodes tab, right click your masternode and click Click the Start Alias.
NOTE: When you are receiving a error message, look here how to solve this problem.
Check the Masternode status: ./gossipcoin-cli masternode status
We can see: “Masternode successfully started”
When not? Check your IP address and masternode private key from the Linux server and the windows wallet.
IP v6 config file example:
rpcuser=username rpcpassword=password bind=[2001:19f0:4400:6139:5400:01ff:fe94:31ed] rpcport=22122 rpcallowip=127.0.0.1 port=22123 listen=1 server=1 daemon=1 logintimestamps=1 maxconnections=256 masternode=1 masternodeaddr=[2001:19f0:4400:6139:5400:01ff:fe94:31ed]:22123 masternodeprivkey=your_private_key