Overview

This section will focus on how to operate full nodes, validators and light clients.

Node Types

We will cover the various types of node types within Tenderdash.

Full Node

A full node is a node that participates in the network but will not help secure it. Full nodes can be used to store the entire state of a blockchain. For Tenderdash there are two forms of state. First, blockchain state, this represents the blocks of a blockchain. Secondly, there is Application state, this represents the state that transactions modify. The knowledge of how a transaction can modify state is not held by Tenderdash but rather the application on the other side of the ABCI boundary.

Note: If you have not read about the seperation of consensus and application please take a few minutes to read up on it as it will provide a better understanding to many of the terms we use throughout the documentation. You can find more information on the ABCI here.

As a full node operator you are providing services to the network that helps it come to consensus and others catch up to the current block. Even though a full node only helps the network come to consensus it is important to secure your node from adversarial actors. We recommend using a firewall and a proxy if possible. Running a full node can be easy, but it varies from network to network. Verify your applications documentation prior running a node.

Seed Nodes

A seed node provides a node with a list of peers which a node can connect to. When starting a node you must provide at least one type of node to be able to connect to the desired network. By providing a seed node you will be able to populate your address quickly. A seed node will not be kept as a peer but will disconnect from your node after it has provided a list of peers.

Sentry Node

A sentry node is similar to a full node in almost every way. The difference is a sentry node will have one or more private peers. These peers may be validators or other full nodes in the network. A sentry node is meant to provide a layer of security for your validator, similar to how a firewall works with a computer.

Validators

Validators sign consensus votes when their pro-tx-hash belongs to the active Dash quorum. All validators have voting power 100; application-provided validator-set updates determine membership. See the validator guide and the canonical validator-set rules.