Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Skip to content
Welcome to the new Ethereum on ARM documentation!
Ethereum on ARM Documentation
Logo

🚀 Getting Started

  • TL;DR - Quick Summary
  • Introduction
  • Download and Install
  • Running an Ethereum node
  • Quickstart Cheatsheet

ℹ️ Overview

  • Introduction
  • Why Choose ARM Hardware?
  • Recommended Hardware
  • Main Features
  • Project Architecture

⚙️ Running a Node

  • Running a Node
  • Managing Clients
  • Ethereum nodes
  • Running Layer 1 nodes
  • Running Layer 2 nodes
  • Running web3 stack
  • Raspberry Pi 5 Example Setup
  • Running on Testnets

🔒 Staking

  • Staking Guide
  • Solo Staking
  • Lido Liquid Staking
  • Obol DVT Staking
  • Migrating a Validator

🌐 Networks

  • Optimism Superchain
    • Running an Optimism Supernode
    • Running a Guardian Node (Optimism Challenger)
    • Testnet Guide: Multi-Machine Setup
    • Verifying Optimism Challenger
  • Arbitrum
  • Gnosis Chain

🛠️ System Utilities

  • System Utilities
  • PiVPN and WireGuard: “Intra-VPN”
  • Ethereum on ARM Secure Backup Utility (Restic)
  • Node Security
  • Troubleshooting

⚡ Advanced Configuration

  • Advanced Configuration
  • MEV boost
  • Commit-Boost
  • Using Your Node
  • Manual Binary Verification Guide

💻 Contributing

  • Contributing Guidelines
  • Development Guide
  • Sources & Upstream Projects

📦 Packages

  • Packages
    • Commit-Boost
    • Dirk
    • Ethereum Metrics Exporter
    • Ethereum Validator Metrics Exporter
    • Ethereum on ARM Config Sync
    • Ethereum on ARM Monitoring Extras
    • Ethereum on ARM Nginx Proxy Extras
    • Ethereum on ARM Utils
    • MEV-Boost
    • Status Node
    • Vero
    • Vouch
    • Besu
    • Erigon
    • Ethrex
    • Geth
    • Grandine
    • Helios
    • Lighthouse
    • Lodestar
    • Nethermind
    • Nimbus
    • Nimbus Execution
    • Prysm
    • Reth
    • Teku
    • Ethrex L2
    • Fuel Network
    • Layer 2 Packages
      • Arbitrum Nitro
      • Optimism Packages
        • cannon
        • kona
        • op-challenger
        • Op-Geth
        • Op-Node
        • op-program
        • Op-Reth
      • Linea
      • Maru
      • Fuel Network
      • Ethrex L2
      • Juno
      • Madara
      • Pathfinder
    • Juno
    • Linea
    • Madara
    • Maru
    • Arbitrum Nitro
    • Pathfinder
    • dvt-anchor for Debian
    • Service Configuration
    • Service Management
    • Logs
    • Data Directory
    • Obol Charon
    • dvt-ssv
    • Swarm (Bee)
    • Kubo (IPFS)
    • EthStaker Deposit CLI
    • Lido Liquid Staking Infra
    • Merge-Config
    • StakeWise V3 Operator
Back to top
View this page

Recommended Hardware¶

In order to run an Ethereum node with our images, you will need one of these devices:

  • NanoPC T6

  • Rock 5B

  • Orange Pi 5 Plus

  • Raspberry Pi 5

Tip

We strongly recommend NanoPC T6, Rock 5B or Orange Pi 5 Plus boards to run an Ethereum full/staking node.

This is the recommended hardware to run an Execution Layer client + Consensus Layer client. If you don’t know what an Ethereum node is, please visit the Operation Introduction.

Warning

The Raspberry Pi 5 doesn’t have native NVMe disk support. If you own a Raspberry Pi 5 with 16 GB of RAM and want to run a node, you can use our image to do so. If not, we strongly recommend to acquire one of the above devices.

Recommended hardware and settings for running an Ethereum full/staking node on a NanoPC T6 board

  • NanoPC T6 (16GB RAM)

  • MicroSD Card (16 GB Class 10 minimum)

  • NVMe disk 2 TB minimum, 4 TB recommended (M2.2280)

  • Power supply

  • Ethernet cable

  • Port forwarding (see clients for further info)

  • A case with passive heatsink

  • USB keyboard, Monitor and HDMI cable (Optional)

Buy links

NanoPC T6 board 16 GB

Recommended hardware and settings for running an Ethereum full/staking node on a Rock 5B board

  • Rock 5B board (16GB to 32GBRAM)

  • MicroSD Card (16 GB Class 10 minimum)

  • NVMe disk 2 TB minimum, 4 TB recommended (M2.2280)

  • Power supply (Radxa official)

  • Ethernet cable

  • Port forwarding (see clients for further info)

  • A case with passive heatsink

  • USB keyboard, Monitor and HDMI cable (Optional)

Buy Links

BOARD

  • Rock 5B board 16 GB

  • Radxa power supply

CASES (Choose one)

  • Acrylic protector with passive heatsink

  • Aluminum case with passive/active cooling

Recommended hardware and settings for running an Ethereum full/staking node on a Orange Pi 5 Plus board

  • Orange Pi 5 Plus board (16GB to 32GB RAM)

  • MicroSD Card (16 GB Class 10 minimum)

  • NVMe disk 2 TB minimum, 4 TB recommended (M2.2280)

  • Power supply

  • Ethernet cable

  • Port forwarding (see clients for further info)

  • A case with passive heatsink

  • USB keyboard, Monitor and HDMI cable (Optional)

Buy Links

  • Orange Pi 5 Plus official page

  • Orange Pi 5 Plus Case with heatsink

Recommended hardware and settings for running an Ethereum full/staking node on a Raspberry Pi 5 board

  • Raspberry Pi 5 board (16GB RAM)

  • MicroSD Card (16 GB Class 10 minimum)

  • NVMe disk 2 TB minimum, 4 TB recommended (depends on Hat)

  • NVMe Hat

  • Power supply

  • Ethernet cable

  • Port forwarding (see clients for further info)

  • A case with passive heatsink

  • USB keyboard, Monitor and HDMI cable (Optional)

Buy Links

  • Raspberry Pi 5 official page

  • NVMe Hat (tested in our labs): GeeekPi N04 and Geekworm X1001

  • Case with Heatsink: GeekPi and Geekworm cases

Warning

IMPORTANT for Raspberry Pi 5

Make sure to buy a disk that doesn’t use a Phison controller. Take a look at the SSD list below and see the Controller column of each disk.

The key components are the NVMe disk and the RAM memory. Please, make sure you get a board with 16 GB of RAM.

Before getting the NVMe disk, please check these 2 sites and look for Mid-Range or High-End :

  • SSD list

  • Great and less great SSDs for Ethereum nodes

Next
Main Features
Previous
Why Choose ARM Hardware?
Copyright © 2024-present, Ethereum on ARM
Made with Sphinx and @pradyunsg's Furo