This page shows you how to launch an Extdev Testnet node from the jump start.

Hardware Requirements

The minimum hardware requirements are as follows: 2 CPU, 16 GB RAM, NVMe SSD. Example: AWS i3.large.

Download the Latest Extdev Stable Build

wget https://downloads.loomx.io/loom/linux/extdev-stable/loom
chmod +x loom

Download the Jump Start Archive

There are two available locations where you can download it from, USA or Singapore. Choose the location closest to you. The Singapore location is automatically replicated from the USA location so it might be a while before it becomes available when we update the archive.

United States


Extract the Archive

tar xfvz extdev-plasma-us1-jump-start.tar.gz

Generate the Unique Config

mkdir blank
cd blank
cp ../loom-jump-start/loom.yml .
../loom init
cp chaindata/config/{priv_validator.json,node_key.json} ../loom-jump-start/chaindata/config/
cd ../loom-jump-start

Start the Node

NOTE: Check the open files limit on your system before starting the node! See Open Files Limit.

Now, let's start the node by running:

../loom run --persistent-peers tcp://[email protected]:46656,tcp://[email protected]:46656,tcp://[email protected]:46656,tcp://[email protected]:46656


The non-validator node will now sync with the validator nodes. Status can be queried at http://localhost:46658/rpc/status

Run Loom as a Service on Ubuntu 16.04 (Optional)

Create /etc/systemd/system/loom.service


User=<user that runs loom>
WorkingDirectory=<working directory of loom>
ExecStart=<path to loom>/loom run --persistent-peers tcp://[email protected]:46656,tcp://[email protected]:46656,tcp://[email protected]:46656,tcp://[email protected]:46656


Reload the Config

systemctl daemon-reload

Run Loom on Boot

systemctl enable loom.service

To start/stop/restart the Service

systemctl (start/stop/restart) loom.service

Inspect the Logs (Method 1)

tail -f /var/log/syslog

Inspect the Logs (Method 2)

sudo journalctl -u loom.service -f

The Open Files Limit

When using systemd, the open files limit is taken care of by the LimitNOFILE directive. It will not, however, be applied when running loom manually.

The system-wide Limit

Add the following lines to /etc/sysctl.conf


To activate it immediately:

sudo sysctl -p

To check whether it is active:

cat /proc/sys/fs/file-max

For a Specific User

Add the following lines to the /etc/security/limits.conf file:

username        hard nofile 500000
username        soft nofile 500000

Note: The user needs to re-login to have it active

To check whether it is active:

# check soft limit
ulimit -Sn

# check hard limit
ulimit -Hn