Run a ParaTime Client Node
This page describes how to run a ParaTime client node on the Oasis Network.
These instructions are for setting up a ParaTime client node which only observes ParaTime activity and can submit transactions. If you want to run a ParaTime node instead, see the instructions for running a ParaTime node. Similarly, if you want to run a validator or a non-validator node instead, see the instructions for running a validator node or instructions for running a non-validator node.
If you are looking for some concrete ParaTimes that you can run, see the list of ParaTimes and their parameters.
Oasis Core refers to ParaTimes as runtimes internally, so all configuration options will have runtime in their name.
This guide will cover setting up your ParaTime client node for the Oasis Network. This guide assumes some basic knowledge on the use of command line tools.

Prerequisites

Before following this guide, make sure you've followed the Prerequisites and Run a Non-validator Node sections and have:
  • Oasis Node binary installed and configured on your system.
  • The chosen top-level /node/ working directory prepared. In addition to etc and data directories, also prepare the following directories:
    • bin: This will store binaries needed by Oasis Node for running the ParaTimes.
    • runtimes: This will store the ParaTime binaries and their corresponding signatures (if they are running in a Trusted Execution Environment).
Feel free to name your working directory as you wish, e.g. /srv/oasis/.
Just make sure to use the correct working directory path in the instructions below.
  • Genesis file copied to /node/etc/genesis.json.
Reading the rest of the ParaTime node setup instructions may also be useful.
To speed up bootstraping your new node, we recommend copying node's state from your existing node or syncing it using state sync.
Running a ParaTime client node doesn't require registering an entity or its nodes.
It also doesn't require having any stake.
Running a client node for a ParaTime that runs in a Trusted Execution Environment (TEE) doesn't require having the same TEE available on the ParaTime client node.
For example, running a ParaTime client node for an SGX-enabled ParaTime like Cipher doesn't require having SGX on the ParaTime client node.

The ParaTime Identifier and Binary

In order to run a ParaTime node you need to obtain the following pieces of information first, both of these need to come from a trusted source:
  • The ParaTime Identifier is a 256-bit unique identifier of a ParaTime on the Oasis Network. It provides a unique identity to the ParaTime and together with the genesis document's hash serves as a domain separation context for ParaTime transaction and cryptographic commitments. It is usually represented in hexadecimal form, for example: 8000000000000000000000000000000000000000000000000000000000000000
  • The ParaTime Binary contains the executable code that implements the ParaTime itself. It is executed in a sandboxed environment by Oasis Node and its format depends on whether the ParaTime is running in a Trusted Execution Environment (TEE) or not.
    For ParaTime client nodes, one does not need to run the SGXS binary, even for ParaTimes running in a TEE. ParaTime client node always runs the regular Linux executable (an ELF binary, usually without an extension).
Like the genesis document, make sure you obtain these from a trusted source.

Compiling the ParaTime Binary from Source Code

In case you decide to build the ParaTime binary from source yourself, make sure that you follow our guidelines for deterministic compilation to ensure that you receive the exact same binary.

Install ParaTime Binary

For each ParaTime, you need to obtain its binary and install it to runtimes subdirectory of your node's working directory.

Install Bubblewrap Sandbox (at least version 0.3.3)

ParaTime client nodes execute ParaTime binaries inside a sandboxed environment provided by Bubblewrap. In order to install it, please follow these instructions, depending on your distribution:
Ubuntu 18.10+
Fedora
Other Distributions
1
sudo apt install bubblewrap
Copied!
1
sudo dnf install bubblewrap
Copied!
On other systems, you can download the latest source release provided by the Bubblewrap project and build it yourself.
Make sure you have the necessary development tools installed on your system and the libcap development headers. On Ubuntu, you can install them with:
1
sudo apt install build-essential libcap-dev
Copied!
After obtaining the Bubblewrap source tarball, e.g. bubblewrap-0.4.1.tar.xz, run:
1
tar -xf bubblewrap-0.4.1.tar.xz
2
cd bubblewrap-0.4.1
3
./configure --prefix=/usr
4
make
5
sudo make install
Copied!
Note that Oasis Node expects Bubblewrap to be installed under /usr/bin/bwrap by default.
Ensure you have a new enough version by running:
1
bwrap --version
Copied!
Ubuntu 18.04 LTS (and earlier) provide overly-old bubblewrap. Follow Other Distributions section on those systems.

Configuration

In order to configure the ParaTime client node, create the /node/etc/config.yml file with the following content:
1
datadir: /node/data
2
3
log:
4
level:
5
default: info
6
tendermint: info
7
tendermint/context: error
8
format: JSON
9
10
genesis:
11
file: /node/etc/genesis.json
12
13
consensus:
14
tendermint:
15
p2p:
16
# List of seed nodes to connect to.
17
# NOTE: You can add additional seed nodes to this list if you want.
18
seed:
19
- "{{ seed_node_address }}"
20
21
runtime:
22
supported:
23
# List of ParaTimes that the node should support.
24
- "{{ runtime_id }}"
25
26
paths:
27
# Paths to ParaTime non-SGX binaries for all of the supported ParaTimes.
28
"{{ runtime_id }}": {{ non-sgx_runtime_bin_path }}
29
30
worker:
31
32
storage:
33
enabled: true
34
checkpoint_sync:
35
disabled: true
36
37
p2p:
38
# External P2P configuration.
39
enabled: true
40
Copied!
Before using this configuration you should collect the following information to replace the variables present in the configuration file:.

Starting the Oasis Node

You can start the node by running the following command:
1
oasis-node --config /node/etc/config.yml
Copied!

Checking Node Status

To ensure that your node is properly connected with the network, you can run the following command after the node has started:
1
oasis-node control status -a unix:/node/data/internal.sock
Copied!
Last modified 13d ago