This is for setting up a full node, a resource-intensive process that requires a persistent server. If you're just trying to use Terra blockchain without downloading the entire blockchain, you're probably looking for Terra Station.
# Hardware Requirements
We recommend the following for running Terra Core:
- 2 or more CPU cores
- At least 300GB of disk storage
- At least 2.5 - 5mbps network bandwidth
# Building Terra Core
# Step 1. Install Golang
Go v1.13.1 or higher is required for Terra Core.
If you haven't already, install Golang by following the official docs. Make sure that your
GOBIN environment variables are properly set up.
# Step 2: Get Terra Core source code
git to retrieve Terra Core from the official repo, and checkout the
master branch, which contains the latest stable release. That should install the
git clone https://github.com/terra-project/core/ cd core git checkout master
# Step 3: Build from source
You can now build Terra Core. Running the following command will install executables
terrad (Terra node daemon) and
terracli (CLI for interacting with the node) to your
# Step 4: Verify your installation
Verify that everything is OK. If you get something like the following, you've successfully installed Terra Core on your system.
terrad version --long terracli version --long name: terra server_name: terrad client_name: terracli version: 0.3.0-24-g3684f77 commit: 3684f77faadf6cf200d18e15763316d5d9c5a496 build_tags: netgo,ledger go: go version go1.13.4 darwin/amd64
# Production Environment
This guide only covers general settings for a production-level full node. You can find further details on considerations for operating a validator node in our Validator Guide
For the moment, this guide has only been tested against RPM-based Linux distributions.
# Increase Maximum Open Files
terrad can open more than 1024 files (which is default maximum) concurrently.
You wil want to increase this limit.
/etc/security/limits.conf to raise the
* soft nofile 65535 * hard nofile 65535
# Create a Dedicated User
terrad does not require the super user account. We strongly recommend using a normal user to run
terrad. However, during the setup process you'll need super user permission to create and modify some files.
# Firewall Configuration
terrad uses several TCP ports for different purposes.
26656is the default port for the P2P protocol. This port is opened in order to communicate with other nodes, and must be open to join a network. However, it does not have to be open to the public. For validator nodes, we recommend configuring
persistent_peersand closing this port to the public.
26657is the default port for the RPC protocol. This port is used for querying / sending transactions. In other words, this port needs to be opened for serving queries from
terracli. It is safe to NOT to open this port to the public unless you are planning to run a public node.
1317is the default port for Lite Client Daemon (LCD), which can be executed by
terracli rest-server. LCD provides HTTP RESTful API layer to allow applications and services to interact with your
terradinstance through RPC. Check the Terra REST API for usage examples. You don't need to open this port unless you have use of it.
26660is the default port for interacting with the Prometheus database which can be used for monitoring the environment. This port is not opened in the default configuration.
# Running Server as a Daemon
It is important to keep
terrad running at all times. There are several ways to achieve this, and the simplest solution we recommend is to register
terrad as a
systemd service so that it will automatically get started upon system reboots and other events.
# Register terrad as a service
First, create a service definition file in
# Sample file:
[Unit] Description=Terra Daemon After=network.target [Service] Type=simple User=terra ExecStart=/data/terra/go/bin/terrad start Restart=on-abort [Install] WantedBy=multi-user.target [Service] LimitNOFILE=65535
Service section from the given sample above to suit your settings.
Note that even if we raised the number of open files for a process, we still need to include
After creating a service definition file, you should execute
# Controlling the service
systemctl to control (start, stop, restart)
# Start systemctl start terrad # Stop systemctl stop terrad # Restart systemctl restart terrad
# Accessing logs
# Entire log journalctl -t terrad # Entire log reversed journalctl -t terrad -r # Latest and continuous journalctl -t terrad -f