Avado Documentation
  • Your AVADO
    • Welcome to AVADO
      • Protect your AVADO
      • The AVADO NFT
    • Connecting to your AVADO
      • Quick Access via AVADO Wi-Fi
      • Set up Remote Connect + ZeroTier
    • Finding Your Way Around
      • The Home Page and Menus
      • The DApp Management Page
    • AVADO Support Community
      • AVADO Praise
      • Beware of Scammers
  • Staking Ethereum
    • ETH Staking Overview
    • Setting up the ETH Clients
      • Configuring the Consensus Client
      • Syncing the Consensus Client
        • Teku
        • Prysm
        • Nimbus
      • Syncing the Execution Client
        • Geth
        • Nethermind
    • Solo Staking (32 ETH)
      • Generate Keys
        • Re-generate or Generate More Keys
      • Deposit 32 ETH
      • Import Validator Keys
      • Monitor Your Node
      • Rewards and Penalties
      • Set up MEV-Boost
      • Set Withdrawal Address
      • Exit from a Solo Validator
    • Rocketpool (8 or 16 ETH)
      • Setting up a Rocketpool Node
      • Add Minipool
      • Backup and Restore
      • Monitor Your Rocketpool Validators
      • Rocketpool Rewards
      • Exit Your Minipools
      • Rocketpool FAQ
    • Stader (4 ETH)
  • More Staking Opportunities
    • Gnosis Staking
      • Getting Started on Gnosis Chain
      • Setting up the Gnosis Clients
      • Generate Keys (Gnosis)
      • Deposit 1 GNO
      • Import Validator Keys
      • Monitor Your Node
      • Rewards and Penalties
      • Set Withdrawal Address
      • Exit from a Gnosis Validator
    • Avalanche Staking
    • Qtum Staking
  • Quick Help
    • Frequently Asked Questions
    • Connection Troubleshooting
    • Attestation Troubleshooting
    • Opening Network Ports
    • Teku Zero Sync
    • Switching from Prysm to Teku, etc.
    • Use Metamask with your AVADO
    • Help with Wi-Fi Password
    • Resetting your BIOS
    • Delivery and Return
Powered by GitBook
On this page
  • Step 1: Install Gnosis Nethermind
  • Step 2: Install Gnosis Teku
  • Step 3: Set Fee Recipient Address in Gnosis Teku
  • Step 4: Syncing Gnosis Teku
  • Step 5: Syncing Gnosis Nethermind
  • Next Steps
  1. More Staking Opportunities
  2. Gnosis Staking

Setting up the Gnosis Clients

PreviousGetting Started on Gnosis ChainNextGenerate Keys (Gnosis)

Last updated 1 year ago

To start validating, you need to install both the Execution Client (Gnosis Nethermind) and the Consensus Client (Gnosis Teku) on your AVADO machine. These two pieces of software work together to perform your validator duties.

During the initial setup, they will download and process all existing information from the Gnosis blockchain to ensure they have an accurate and up-to-date local copy of the Gnosis state. This process is known as "syncing".

The Consensus Client will need to sync up first, and this is a relative fast process that can complete within a few minutes with Gnosis Teku. Syncing Gnosis Nethermind will take more time, usually a day or two, as it involves downloading and processing a substantial amount of data.

Keep your device cool!

During the initial sync of a blockchain, your system will operate at full capacity for multiple hours. It is crucial to maintain an optimal temperature to prevent any potential heat damage. If you are using the AVADO i7 model, which features a fan-less design with cooling fins, we recommend using a USB fan to provide additional cooling support during this initial sync process. This will help ensure that your system stays cool and operates efficiently throughout the syncing period.

Step 1: Install Gnosis Nethermind

Navigate to the DappStore and locate the DApp named Gnosis Execution Client (Nethermind) and click Install.

After installing Gnosis Nethermind, it will automatically start running, but it won't be able to sync until a Consensus Client is installed and synced. This will be our the next step.

Step 2: Install Gnosis Teku

Navigate to the DappStore and locate the DApp named Gnosis Validator + Beacon Chain (Teku) and click Install.

Once installed, you can open the Gnosis Teku DApp by:

The DApp has two sub-menus: Main, and Settings.

If you're using a phone or tablet, the sub-menus may be hidden. Look for the button that has three horizontal lines, on the right-hand side of the screen. Click to expand it. The expanded sub-menu can be found on the left-hand side of the screen (you may need to scroll across to see it).

Step 3: Set Fee Recipient Address in Gnosis Teku

Gnosis Teku will prompt you to set up a default Fee Recipient Address.

What is the Fee Recipient Address?

When you start validating, there will be two streams of rewards:

  • Consensus Layer rewards: These are regular rewards (in GNO) paid to you for performing validator duties, such as producing attestations, and making proposals. These rewards accrue on your validators and are regularly "skimmed" to your Withdrawal Address (which you will set separately).

  • Execution Layer rewards: These are occasional rewards (transaction fees, in xDAI) paid to you when you get a chance to make a block proposal. These rewards are immediately available and are sent to your Fee Recipient Address.

The Fee Recipient Address is where you would receive your Execution Layer rewards. Please make sure that you:

  • Use a Gnosis address you own and control, preferably a hardware wallet address.

  • Do not use an exchange address, as most exchanges are not set up to recognize staking rewards and you will very likely lose your rewards.

For your consideration:

  • You can change the default Fee Recipient Address any time.

  • You can set the Fee Recipient Address for individual validators any time, overriding the default.

  • You can use different Fee Recipient Addresses for individual validators, if you wish.

  • You can set the Fee Recipient Address to be the same as your Withdrawal Address (to be set separately), if you wish.

To set the Fee Recipient Address, enter or paste-in your Gnosis address into the box indicated in the figure below. Then click Apply changes.

Step 4: Syncing Gnosis Teku

Gnosis Teku will need to sync up first. Thanks to Checkpoint Sync, the Consensus Clients start with a recently finalized checkpoint state and only need to catch up to the current head of the blockchain. This process is relatively fast, usually taking only a few minutes.

Step 5: Syncing Gnosis Nethermind

Syncing Gnosis Nethermind is the process by which the it catches up to the latest Gnosis block and synchronizes its global state. It is a time-consuming process, typically taking many hours to a few days depending on your network speed. It's important to be patient during this period.

Next Steps

Congratulations for setting up your Gnosis node!

Now that you have the basic infrastructure in place, you can proceed to the actual staking. Follow our guide on the next step to generate validator keys.

Clicking the button for the DApp on the Home Page; or

Clicking the DETAILS button for the DApp on DappStore, then click ; or

Clicking the name of the DApp, or its button, on the My Dapps menu (figure below).

Gnosis Teku's syncing process closely resembles that of Ethereum. For a better understanding of what to expect during the syncing process and for troubleshooting guidance, please refer to the " section.

If everything goes smoothly, the will indicate that the Execution Client is online, the Beacon Chain syncing process has begun, and shortly after, the syncing will be completed. At that point, Gnosis Teku will be waiting for the Execution Client to finish its syncing process.

Gnosis Nethermind's syncing process closely resembles that of Ethereum. For a better understanding of what to expect during the syncing process and for troubleshooting guidance, please refer to the " section.

To ensure a smooth syncing experience, we recommend familiarizing yourself with the sync process and actively monitoring the . By doing so, you can gain confidence in determining whether the syncing process is progressing smoothly or if any issues require your attention.

Open
Configure Package
Open
Syncing the Consensus Client - Teku
Logs
Syncing the Execution Client - Nethermind
Logs