Skip to main content

Run a Node

Image: Gnosis nodes around the world, circa Nov 2022 (source: Nodewatch)

A Community-run Chain

  • Gnosis is a community-run chain that is created by nodes run by thousands of ordinary people around the globe. As a distributed network, a diverse set of nodes ensure that the network is resilient to technical failures. A diversity of nodes run across many countries ensures the network can remain credibly neutral infrastructure.
  • Running a node is perhaps the most profound way to contribute to a blockchain network. By running a node, you -are- the network. Together with other nodes run by others around the planet, you form part of a global network that is anti-fragile and resilient.
  • Gnosis has a strong culture of homestakers running nodes from their homes, that are not reliant on cloud providers or datacenters.
  • Gnosis has a stretch goal to have a node in every country by 2025.

Gnosis vs. Ethereum

  • Gnosis runs the same composite client software and tooling stack as Ethereum
  • In some cases, Gnosis clients are just Ethereum clients run with a --network flag! (e.g. Nethermind, Lighthouse, etc)
  • Gnosis aims to to be a learning ground for a new generation of node runners, requiring only 1 GNO (~$100 at Nov 2022) instead of the 32 ETH (~$38,400 at Nov 2022) minimum required for Ethereum
  • Gnosis runs the same client software as Ethereum, with minor parameter tweaks. As such, Gnosis is a Proof-of-Stake network that uses Ethereum's Beacon Chain consensus.

Proof-of-Stake

caution

Validator deposits are currently one-way, non-reversible transactions. Similar to Ethereum, no concrete date has been set for withdrawals of GNO staked in validators.

  • Gnosis minimum stake is 1 GNO to run a validator.
  • 1 GNO is turned into 32 mGNO, to mirror the 32 ETH for Ethereum staking
  • Nodes receive rewards for being an active validator, and suffer penalties for malicious or negligent behavor.

Approaches

Running a node involves significant technical complexity. Gnosis provides both beginner-friendly "1-click" tools that abstract the complexity in favor of defaults, and a full advanced guide for technical users.

1-click Tools

Gnosis supports several beginner-friendly "1-click" tools for running a node. This allows non-technical users to also run a node, lowering the barrier to entry for participation.

caution

1-click tools are fine for running a basic validator or node. For more complex use cases which require customization, please refer to the Guide)

  • Dappnode is a dashboard that abstracts away all the technical complexity of running a node. Users pick which client to run, and install and manage it with a click of a button. Users can purchase pre-configured hardware with Dappnode installed, or install it on any Linux machine.
  • Nethermind Sedge is a tool that allows users to generate Dockerfiles based on their desired configuration and client choices. More advanced users can also use this as a starting point and modify the Dockerfiles to their needs.
  • Stereum (in progress)

Guide

See our full end-to-end setup guide.

Requirements

Hardware

Gnosis is designed to run on average consumer-grade computers. It's recommended to run a node on dedicated hardware to eliminate the performance impact on their machine and minimize node downtime.

We recommend Rocketpool's excellent guide that explains hardware requirements for running a node. Generally, nodes require:

  • CPU with at least 4 threads
  • At least 16 GB of RAM
  • NVMe SSD (preferred) or SATA SSD

Requirements vary client to client, for more detail see the associated system requirements below.

Execution Layer
NethermindNethermind: System Requirements
BesuBesu: System Requirements
ErigonErigon: System Requirements
GethGeth: Hardware
Consensus Layer
LighthouseLighthouse: System Requirements
LodestarLodestar: Specifications
NimbusNimbus: Hardware
TekuTBD
PrysmPrysm: Prerequisites

Network Connectivity

Running a node requires a reliable internet connection, as nodes are constantly exchanging data across the peer-to-peer network. Brief offline periods will result in small inactivity penalties, but this will typically be recouped quickly as long as the outage is short.

A Gnosis node with an average number of peers consumes approximately 700 mb/hour of upload bandwidth, and this may increase with time. Note that syncing the execution layer of Gnosis may take up to 1-3 days, depending on your setup.

For better understanding of the network throughput requirements, a benchmark was conducted on the Lighthouse v2.2.1 client running a GBC on 4th May 2022. The client was configured to maintain 100 simultaneous peer connections. Inbound and outbound traffic consumption was measured while altering the number of active validators connected to the beacon node.

Validators are advised to consider those numbers when planning their infrastructure and budget. With growth of the overall validator set, these requirements will increase over time as well. Make sure to allocate enough spare resources to account for future network growth.

Number of validatorsInbound trafficOutbound trafficApproximate monthly traffic
101.0 MB/s1.8 MB/s7.2 TB
322.4 MB/s3.15 MB/s14.2 TB
644.5 MB/s3.8 MB/s21.2 TB
1284.6 MB/s3.8 MB/s21.5 TB
>2564.6 MB/s3.9 MB/s21.7 TB