Node Setup Manual (testnet)

How to Operate Tellor Layer Node.

Recommended Hardware Specs

Operating a node for a personal RPC can be done using most modern computers.

For running a validator, more power is recommended:

• Modern cpu with at least 8 cores / threads

• ram: 32 gb + (16gb swap space recommended)

• storage: 1000gb+ @ NVME gen4

• network: 500mb/s DL, 100mb/s UL (the faster the better)

Software Prerequisites

Linux

jq, yq, sed, curl, wget, make, and Go are required for running the various config scripts and commands in this guide:

sudo apt install jq yq sed curl wget build-essential

Install go if you want to build binaries from the layer repo:

• Go version 1.22 : Use the default install instructions here.

MacOS

• Commands shown should just work while logged in as a user (not root).

• If you are using an older Mac with an intel chip, the linux versions (amd64) in step 1 below may be used. (just remember to use the mac commands!)

• If on raspberry pi or similar, use the binary downloads for "arm64".

Choose How you will Sync your Node

There are two ways to get a node running on layertest-5:

• State Sync: Your node is configured with seeds and peers from which it will try to download recent chain state snapshots. This sync method is faster, but you will not be able to query block info (like transactions) for any blocks that were produced before the day of your sync.

• Genesis sync: Your node will start with the genesis binary and sync the entire chain. A different binary will be needed for each upgrade since genesis. This sync method can take a long time depending on how long layertest-5 has been live.

1. Download and Organize the layerd Binary(s)

Be sure to select the tabs that work for your setup! You will get errors if you use the linux commands on mac and vice-versa.

State Sync

First, download the binary from the Tellor Github.

Linux

mkdir -p ~/layer/binaries && cd ~/layer/binaries && mkdir v6.1.5 && cd v6.1.5 && wget https://github.com/tellor-io/layer/releases/download/v6.1.5/layer_Linux_x86_64.tar.gz && tar -xvzf layer_Linux_x86_64.tar.gz

MacOS

Linux ARM64

Initialize .layer folder in your home directory: layerd init [moniker] [flags]

./layerd init layer --chain-id layertest-5

2. Set System Variables for Layerd

A Layer node uses the following variables:

• TOKEN_BRIDGE_V2_ADDRESS: the token bridge contract address.

Edit .bashrc or .zshrc file with a text editor like nano:

Linux

nano ~/.bashrc

MacOS

Add this line to the bottom of the file.

export TOKEN_BRIDGE_V2_ADDRESS="0x55355157703A44f7516FBB831333317E98944e32"

Exit nano with ctrl^x then enter y to save the changes.

Load the new variables:

Linux

source ~/.bashrc

MacOS

3. Edit Chain Configuration for Tellor.

We need to open up the tellor layer config files and change some variables. You can use any local text editor like code, vim, or nano.

Note: All variables not shown can be safely left as is.

To open the API up to the local network or set a custom port: In ~/.layer/config/app.toml:

# Address defines the API server to listen on.
address = "tcp://0.0.0.0:1317"
#...

In ~/.layer/config/client.toml:

#...
# The network chain ID
chain-id = "layertest-5"
# Set your chosen keyring backend (optional).
keyring-backend = "test"

In ~/.layer/config/config.toml:

#...
# TCP or UNIX socket address for the RPC server to listen on (optional)
laddr = "tcp://0.0.0.0:26657"
#...
# Use '["*"]' to allow any origin
cors_allowed_origins = ["*"]
#...
# Comma separated list of nodes to keep persistent connections to
persistent_peers = "ac7c10dc3de67c4394271c564671eeed4ac6f0e0@34.229.148.107:26656,8d19cdf430e491d6d6106863c4c466b75a17088a@54.153.125.203:26656,c7b175a5bafb35176cdcba3027e764a0dbd0811c@34.219.95.82:26656,05105e8bb28e8c5ace1cecacefb8d4efb0338ec6@18.218.114.74:26656,705f6154c6c6aeb0ba36c8b53639a5daa1b186f6@3.80.39.230:26656,1f6522a346209ee99ecb4d3e897d9d97633ae146@3.101.138.30:26656,3822fa2eb0052b36360a7a6e285c18cc92e26215@175.41.188.192:26656"
#...
# How long we wait after committing a block, before starting on the new
# height (this gives us a chance to receive some more precommits, even
# though we already have +2/3).
timeout_commit = "1s"
#...

Note: Peer connection errors can be normal for a few minutes after start.

4. Sync the Node

Before starting your node, it's a good idea to think about how you want to run it so that the process does not get killed accidentally. This is not obvious for beginners. Try GNU screen or tmux. More advanced setups can be achieved using systemd services.

Choose the tab depending on whether or not you are doing a genesis sync, or a state sync:

State Sync

We need to make a few more config edits to make sure your state sync goes smoothly.

1. To find a good trusted height to use for a snapshot sync, we need to find the height of a snapshot available from https://node-palmito.tellorlayer.com/rpc/ . Copy and paste this entire block of commands into a terminal and hit enter:

export LATEST_HEIGHT=$(curl -s https://node-palmito.tellorlayer.com/rpc/block | jq -r .result.block.header.height); \
export TRUSTED_HEIGHT=$((LATEST_HEIGHT - 17500)); \
export TRUSTED_HASH=$(curl -s "https://node-palmito.tellorlayer.com/rpc/block?height=$TRUSTED_HEIGHT" | jq -r .result.block_id.hash); \
echo $TRUSTED_HEIGHT $TRUSTED_HASH

The output should be something like:

trusted_height: 3785000
Trusted_hash: DD27874AB1F5F4DFC5D7818E7CFBF8A8ECEDA745FFA78DF24D799B2B201418B9

1. Edit config.toml:

Open your config file:

nano ~/.layer/config/config.toml

Scroll or search (ctrl^w) the file and edit the state sync variables shown here to match the trusted height and trusted hash you found above:

# [statesync]
# ...
enable = true
#...
rpc_servers = "https://node-palmito.tellorlayer.com/rpc/,https://node-palmito.tellorlayer.com/rpc/"
trust_height = 3785000
trust_hash = "DD27874AB1F5F4DFC5D7818E7CFBF8A8ECEDA745FFA78DF24D799B2B201418B9"
trust_period = "168h0m0s"

Be sure to replace the trust_height and trust_hash with the block number and hash from the curl command above.

Exit nano with ctrl^x then enter y to save the changes.

1. Start your node:

./layerd start --home ~/.layer --key-name ACCOUNT_NAME --keyring-backend test --api.enable --api.swagger

The node should start up quickly and begin downloading snapshots from peers.

Some errors related to peer connections can be expected even if the snapshot sync is working properly. (e.g. "we need more peers", or "Failed to reconnect")