Create your own Akroma ($AKA) Masternode in 10 minutes
So I’ve finally gotten around to setting up my very first masternode, after contemplating it for a while.
I’m not going to go in to very detailed specifics about what masternodes are in this article, it is far better explained in articles just a quick Google search away. I’m just gonna do a plain and simple write-up of my own Akroma MN experience.
I have just recently become aware of this project, and I like what I see, so there is no good reason why Akroma should not be my first Masternode setup.
For more info about Akroma, check their website, my initial impression is that this is a very promising project with a solid team.
Akroma Masternodes require 5001 AKA, so the first thing I did was to visit an Exchange, Graviex and Stocks.Exchange are listing, at the moment. Which cost me about 0.150 BTC at the time of writing (give or take).
Next up is configuring a server. I’m pretty customed to running different flavours of Linux OS’es, so for the purposes of writing this article — and until I can decide where to put this masternode permanently — I’ll just set it upon a Ubuntu VM running on my Mac.
This makes it easy for me, I have a blank VM ready for test projects almost all the time — and this Github article from the team more or less finishes the job for me. After having a machine ready to run the masternode from, the below comments were all I needed to enter in Linux before my Masternode was up and running:
apt-get install sudo
sudo adduser akromauser # this can be any username you want
sudo adduser akromauser sudo
sudo adduser akromauser systemd-journal
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install wget curl unzip systemd -y
sudo wget https://raw.githubusercontent.com/akroma-project/akroma-masternode-management/master/scripts/debian/setup.sh
sudo chmod +x setup.sh
sudo ./setup.sh --systemd
sudo systemctl start akromanode
sudo systemctl enable akromanode
sudo wget https://raw.githubusercontent.com/akroma-project/akroma-masternode-management/master/scripts/any/utils.sh
sudo chmod +x utils.sh
./utils.sh — enodeId — nodePort — nodeIp
You’ll have to follow the instructions in the linked Github article, of course — but that was it. I filled 5001 AKA in a wallet, and ran those 15 commands on a Linux server, verified account ownership with one transaction (as described on Github) and I was up and running. You can get a server to run such a Masternode on a 12 month free trial from Amazon, if you choose the right tier-server. It will only take you around 15 minutes more, to have a MN set up at a cloud provider at little to no cost.
So, if I were you, I’d drop a dime or two in my tip jar (see below) and go right ahead and set up your own Masternode in 10 minutes. I’m pretty confident you’ll appreciate doing that, sometime in the not to distant future😏
Tip jar (much obliged):
AKA: 0xfE6d5EB3853B68BC2aFE8BA47eFdb9ABCb618f51
XHV: hvxyCxSYVGLSysjcLhRUhEfpHX3p9wXjpGNFC7iR84DPewEuZ3BxoYAaC7uUVvMxxVVBWwsxWkzPLPfFqwtVxveE7S9tdCbok4
BTC: 14iKgia5wtdjmLXs7QiJui3Sb6KVP6XebL
ETH: 0x913c1CD95Dc971B304C5217831102E350230efaB
BCH: qq5tjpm0jv460tvk4pa050pwc6u2aj46gs2tce2rd4
NEO: ARdd2cqCSajpzkSZGFtSqAPvBLYcquD7WH
Follow me on Twitter for more random stuff
