Module 2: Infrastructure, Hardware & Security Basics

What this module covers

• Where Ethereum validators can run
• Hardware and network requirements
• Preparing and accessing your machine
• Basic security and operational hygiene

Where validators can run

Ethereum validators can run in multiple environments, including:

• Consumer-grade hardware at home
• Cloud servers

Running validators from home strengthens the network by improving decentralization and is encouraged where feasible. That said, many operators (especially professionals) run validators on cloud infrastructure.

Hardware requirements

Exact requirements vary by client and configuration, but a reasonable baseline is:

• CPU: 4+ modern cores
• RAM: 16 GB (ideally 32 GB)
• Storage: 2 TB SSD (ideally 4 TB)
• Network:
• Stable connection
• Low latency preferred
• There’s no strict bandwidth requirements
• High or inexistent monthly data cap (nodes communicate constantly with others and can reach hundreds of GB every month)

Before setting up your machine

Make sure you have:

• An Ethernet cable
• A computer connected to the same network
• Either:
• A monitor with HDMI + keyboard, or
• Access to your router to find the machine's IP address

If you do not have a monitor or do not know how to access your router, ask for help in the cohort Slack channel.

Set up your machine

Follow the official Chainnodes setup guide:

Embed GitHub

The guide covers:

• Installing the system using the provided microSD card
• Booting the machine from its internal drive
• Finding the machine on your network
• Accessing it locally or through SSH
• Changing the default password

If you get stuck at any point, ask in the cohort Slack channel.

Read more here

1. Node hardware requirements https://ethereum.org/developers/docs/nodes-and-clients/run-a-node/
2. Nodes and clients overview https://ethereum.org/developers/docs/nodes-and-clients/

End of the module

Before continuing, make sure:

Execute this step

1. Install the machine

With the machine powered off:

1. Connect the Ethernet cable.
2. Connect the HDMI monitor if you are using one.
3. Insert the provided microSD card into the microSD/TF slot.
4. Connect the power supply.

The first installation stage runs automatically. It installs the operating system onto the internal NVMe drive and then powers the machine off.

When the machine powers off:

1. Disconnect the power.
2. Remove the microSD card.
3. Reconnect the power.

The second installation stage will start automatically.

The machine is ready when the monitor displays:

### STAGE2 complete — node ready.

or:

chainnode login:

The complete installation normally takes approximately 10–15 minutes. Do not disconnect the machine while the installation is running.

2. Access the machine

You can access it directly or remotely.

Option A: Monitor and keyboard

At the login screen, enter:

Username: user
Password: password

The password will not appear while you type. This is normal.

Option B: SSH

Find the machine in your router’s connected-device or DHCP client list.

Its hostname should be:

chainnode

Copy its IP address. It will normally look similar to:

192.168.1.100

Open Terminal on macOS or Linux, or PowerShell/Windows Terminal on Windows, and run:

ssh user@YOUR_MACHINE_IP

For example:

ssh user@192.168.1.100

Use the initial password:

password

If asked whether you want to continue connecting, enter:

yes

The machine’s IP address is also displayed on the HDMI login screen.

3. Change the default password

Immediately after logging in, run:

passwd

Enter the current password, then create a new and unique password.

Do not configure the node or add validator keys while the default password is still active.

Security basics

You do not need to complete every security configuration yet, but you should internalize these rules early.

Validator keys

• Generate validator keys securely
• Never share validator keys
• Never run the same validator keys on two machines at the same time
• Keep secure backups of the keystores and their associated passwords

Machine access

• Change default passwords immediately
• Use SSH key authentication instead of password authentication once it has been configured and tested
• Do not expose SSH or management interfaces directly to the public internet
• Keep the operating system and node software updated

SSH key authentication is recommended even when the machine is only accessible from the local network.

Physical and operational security

• Keep the machine somewhere dry and well ventilated
• Do not disconnect power while the system is running
• Do not install unrelated software on the staking machine
• Do not run commands from unknown or untrusted sources