Akroma Masternode Linux Setup

Our current masternode setup supports Ubuntu/Debian and RedHat/CentOS based distros.

Install on Linux


NOTE: The binaries are tested on CentOS 7.x, Ubuntu 16 and 18, and Debian 9.5; 32 and 64-bit only. Usage on other OS' and architectures are at your own risk.

The recommended method for deploying your masternode instance consists of instantiating a systemd process available to start/stop at will, whilst the alternative consists of just running a standard background process.

If not installed yet, make sure the linux packages wget and sudo are installed prior to executing the proceeding commands.

Proceed with the installation by updating package lists and install required software

Dependency install on Debian or Ubuntu

sudo apt-get update # Update your package lists
sudo apt-get install wget -y # Install required packages for running scripts

Dependency install on RHEL/CentOS

sudo yum update # Update your package lists
sudo yum install wget -y # Install required packages for running script

For running an Akroma masternode on a supported Linux distribution, we recommend running our setup script for bootstrapping a systemd service. While you don’t need to know much about this software, what’s important is that it gives you full control of starting, stopping, and monitoring your masternode process, while making it easy to automatically start it at boot.

Deployment Instructions

We wrote a script that will be used to assist in quick setup, if you want to see this code, it can be found here. This script takes care of everything you need for getting started, as well as some optional parameters. Run the following command for downloading the program we need for setup and management.

wget https://github.com/akroma-project/akroma-masternode-management/releases/download/0.0.7/akroma-mn-setup.x86_64
chmod +x akroma-mn-setup.x86_64
wget https://github.com/akroma-project/akroma-masternode-management/releases/download/0.0.7/akroma-mn-setup.i686
chmod +x akroma-mn-setup.i686

To see all possible options for setup, run this command:

./akroma-mn-setup.x86_64 --help
./akroma-mn-setup.i686 --help

If you're having issues running the scripts, please refer to Known Issues at https://github.com/akroma-project/akroma-masternode-management/blob/master/source/README.rst.

Your output should look like what you see below

usage: akroma-mn-setup.x86_64 [-h] [-i] [-g {latest,stable}] [-s {latest,stable}]
[-r] [-p RPCPORT] [--port PORT] [-u [USER]]
[--rpcuser RPCUSER] [--rpcpassword RPCPASSWORD]
[--no-rpcuser] [--no-rpcpassword] [--ufw]
[--update-only] [-v]
optional arguments:
-h, --help show this help message and exit
-i, --interactive Interactively install/upgrade akromanode (Default:
-g {latest,stable}, --geth {latest,stable}
Geth version to use (Default: stable)
-s {latest,stable}, --scripts {latest,stable}
Script version to use (Default: stable)
-r, --remove Uninstall akromanode (Default: False)
-p RPCPORT, --rpcport RPCPORT
RPC Port (Default: 8545)
--port PORT Network listening port (Default: 30303)
-u [USER], --user [USER]
Run akromanode as non-root user (Default: akroma)
--rpcuser RPCUSER RPC User (Optional)
--rpcpassword RPCPASSWORD
RPC Password (Optional)
--no-rpcuser Remove RPC User/Password (Optional)
--no-rpcpassword Remove RPC User/Password (Optional)
--ufw Configure UFW (Optional)
--update-only Update geth and scripts only. Disables auto-update
-v, --version Script Version

Starting the Akroma Masternode

Simply run the following command for running the default setup.

sudo ./akroma-mn-setup.x86_64
sudo ./akroma-mn-setup.i686

By accepting "Auto-update Akroma MasterNode", you agree to allow a scheduled task to be run daily on your system to ensure that your service file, geth version, setup and utility scripts are kept up-to-date. This scheduled task is randomly generated upon acceptance.

After running akroma-mn-setup.x86_64|i686, both akroma-mn-setup and akroma-mn-utils are added in /usr/sbin and can be ran from that location or simply by typing akroma-mn-setup or akroma-mn-utils.

NOTE: Any subsequent executions of akroma-mn-setup will verify the validity of your service file. Only if new configuration options are provided will your service file be changed and restarted, or in the presence of an updated geth client. If you're having difficulty setting up your firewall, run akroma-mn-setup --ufw, to automatically have it configured for you.

Masternode Registration


Registration of your node allows us to monitor uptime, as well as keep check of wallet balance to ensure you have the necessary collateral.

  1. Login to https://akroma.io

  2. In top navigation, visit “Masternodes” link.

3. You should now see the “Create Masternode” button link, click this.

4. Once on the Create page, you’ll see several fields required for creation.

Overview of these fields

  • Enode Id: Unique public key for your node. We will discuss how to find this below.

  • IP: IP address of your node, remember that static IP mentioned above? This is that.

  • Port: Port used to perform periodic health checks on. Should be 8545 unless specified differently in initial node setup. Make sure this port is open to the outside.

  • Wallet Address: Akroma wallet address associated with your masternode (used for payouts, verification, and checks).

  • Username: The RPC Username you optionally picked during setup.

  • Password: The RPC Password you optionally picked during setup.

We’ve provided a utility program for providing you with the information of Enode ID, IP address, and port as part of the setup and installation.

Enode Id: 732347e467665fe84bd6b2efe944fd96232a2a2266c06efef27867fa988f2ce2020c2e718e63055f1b4f7990ee3ca1c31c70462ceb48d515d070a6e408a199d8
Node IP:
Node Port: 8545
Geth Versions:
current : 0.1.1
latest : 0.1.1
stable : 0.1.1
Service Is-Active: True
Port is open locally: False
Service Error(s):
-- Logs begin at Wed 2018-08-01 02:11:29 UTC, end at Wed 2018-08-01 02:14:32 UTC. --
-- No entries --

Copy/paste or enter this information in its entirety into the masternode form and click the "Create Masternode" button.

At this point, if all of the details are valid, you should have created a masternode, yet to be “verified” as represented in “pending” status.

Before proceeding, make sure your server has it's firewall and network setup properly

  1. Server must allow incoming traffic to your masternodes chosen port (see: this guide)

  2. Server must be tied to a static IP so it can be seen publicly

If these two things are not true, your masternode will not verify.

Masternode Verification


Verification of your masternode consists of one user-interaction. This is sending a transaction from your account to the same account (that is the account being used for the masternode) in any amount of AKA along with the value of Transaction Data (represented as Transaction Data) on the unverified masternode detail page. Copy this value and paste it into the data input in your transaction (not currently available in the Android wallet).

Transaction Data entered into the transaction data field below:

At this point, if your transaction has been sent, and your wallet meets the minimum collateral requirement for verification of 5001 AKA, the masternode should be verified. A background job is run periodically (20 minute intervals) to verify masternodes, which will then pick up your masternode.

Once verified, details will show health check and uptime status, like so.

If your masternode is not verified after following this guide, give it a once over to make sure you didn’t miss any commands, or perform any faulty copy/paste maneuvers. If all else fails, please reach out to the Akroma core team, and we’ll do our best to debug the problem with you.

Masternode Setup Conclusion

This concludes deployment, registration, and verification steps for a masternode on the Akroma network. If you have any questions regarding troubleshooting setup, correction to this guide that we may have not caught, or found bugs in setup or running, please contact us on our Discord here in the #masternodes channel, check out this troubleshooting guide. Thank you and happy masternoding.