Now submit the current page to create your droplet. You’ll be brought to another page where you can see the status of your server as it spins up.

Next, lets configure the firewall to our server. Click into your newly created droplet and go to Networking. Create a new firewall with the settings below for Inbound Rules and assign it to your droplet.

Note: for Apollo nodes, please disregard the settings for HTTP & HTTPS. You will have 3 rows of rules configured instead of the 5 shown below.

For our server’s firewall we want to abide by the principle of least-privilege, which says that we should only allow access to information and resources that are necessary for the purposes we expect. Here the Ambrosus team has outlined these settings as requirements to allow the network to communicate with our node.

Setup Your Node

Now that our server is running, we need to connect to it.

Step 2: Login into your VPS

For Windows Users

You’ll have to use PuTTY to connect to your VPS. Heres a good guide on how to do that in DigitalOcean https://www.digitalocean.com/docs/droplets/how-to/connect-with-ssh/putty/

If you’re familiar with Windows Subsystem for Linux (WSL) and have it set up you can follow the Mac / Linux steps below.

For Mac /Linux Users

Begin by copying the IP address of your droplet. You can find it by viewing your droplet in your browser. Simply click on it to copy it to your clipboard. Next, open your terminal and type in the following command

ssh root@<droplet_ip_address>

Replace “<droplet_ip_address>” with the address we had previously copied. This above command tells us we want to SSH into the root user at the following server IP address. If you setup a password for your SSH key, you’ll be prompted to enter it here. Say yes to any other prompts.

Note that root is a special superuser and is the default user who has all rights or permissions in our Linux operating system.

Just like that you’ll be connected to your VPS. You are now remotely accessing your private server!

If you recall, we setup our server with the Ubuntu OS. Other than the actual operating system, there is nothing else installed on our server. Time to change that.

Step 3: Retrieve and run the setup script

If you’ve been following the ambrosus github, you’ll notice a project called ambrosus-nop. This is the tool created by the team to facilitate onboarding.

Let’s start by downloading this tool into our server. Run the following commands

wget https://nop.ambrosus.com/setup.sh



chmod +x setup.sh

The first command beginning with wget is a utility that retrieves the content of the setup script and related files we’ll need

The second command, chmod simply changes the permissions of the .sh file so that we’ll be able to run the script. The “x” is for executable

Now let’s run this script, its an interactive script so have you’ll be using your up/down arrows along with the enter key to make your selections.

./setup.sh

Options to select:

Main network

Create a new key — this is a Ethereum wallet in case its not clear, we need to either provide a key to an empty wallet we’ve created elsewhere or more simply we can just let the script create the new public/private key for us. We will choose the latter.

IMPORTANT: Do not enter the private key to your Ethereum cold wallet, you will be creating an entirely new wallet above to use with the network

http://<droplet_ip_address> — paste in the IP address to your server that should still be copied onto your clipboard. Don’t forget the “http://” prefix. This is how the network will be able to reach our node.

— paste in the IP address to your server that should still be copied onto your clipboard. Don’t forget the “http://” prefix. This is how the network will be able to reach our node. Email address

Once you complete the script there are two files you should be aware of

1. state.json — this file stores the result of the script you just completed, in here you can find the private and public key to the wallet you had created. Do not share the private key with anybody! The public key will be used for whitelisting below. 2. TOS.txt — this is our signed terms of service agreement. We’ll be copying the contents in the following steps View the contents with the following command cat ./ambrosus-nop/state.json or cat ./ambrosus-nop/output/TOS.txt

Thats it, you’ve now configured your node, time to compile the information needed for whitelisting into a draft email.

Step 3: Create a draft email of our whitelist request

When completing the script, you should see it write out a bunch of text into the terminal. Copy the text beginning with the { and ending with }, see below for an example



network: main,

address: 0x123456789

role: Atlas Omega

email: youremail@gmail.com

url:

...

} network: main,address: 0x123456789role: Atlas Omegaemail: youremail@gmail.comurl: http://127.0.0.1 ...

We need to send this to tech@ambrosus.com. Start an email and title it “Atlas Omega Whitelist Request” or similar and paste in the above text.

In addition to this text, they ask you to submit the signed terms of service agreement. Recall the cat command we used previously to read out the public SSH key. Let’s use that again here.

cat ./ambrosus-nop/output/TOS.txt

Copy the contents of the TOS.txt that were output onto the terminal and create a new text file on your actual desktop machine to save it in.

Lastly, attach the TOS.txt file to your email and save it as a DRAFT

The onboarding process has changed slightly, you now need to have our tokens transferred to native AMB before you can submit our request for whitelisting. Complete the next section before sending out your whitelist request.

At the end of this section you have:

Downloaded the ambrosus-nop tool onto your VPS

Completed the initial setup steps

Prepared a draft of your email for whitelisting

Convert To Native AMB

You most likely have your ERC-20 amb tokens stored somewhere in an Ethereum cold wallet. In this section we’re going to convert these tokens to native AMB which we’ll be able to use in the mainnet.

Step 5: Setup MetaMask and send our ERC-20 tokens

First, download MetaMask to your browser if it is not already installed. https://metamask.io/

Recall the wallet we previously created in Step 3 as part of running the setup script. This is your primary wallet that you be using to store your native AMB. To get there we’ll need to first send our current ERC-20 tokens to this wallet and use the bridge to do the conversion.

Let’s start with importing our new wallet into MetaMask.

First click on the MetaMask extension in your browser, it asks you to create a new wallet or import one with a seed phrase. Since we don’t have a seed phrase for our wallet, just create a new wallet to get to the next screen.

After creating an account, click on the Account button in the upper right corner, you’ll probably have a colorful image there, and select import account.

Here you’ll paste in the private key to your wallet. See below if you are unsure how to get that.