Home

Awesome

DISCLAIMER: This is a legacy repository. Please move to our new one:

https://github.com/diglos/ethereumonarm

Ethereum on ARM64 is a custom Ubuntu Linux image for the NanoPC-T4 ARM SoC [1] and the RockPro64 ARM SoC [2] that runs Geth or Parity Ethereum clients as a boot service and automatically turns the device into a full Ethereum node. It includes other components of the Ethereum ecosystem such as Trinity, Status.im, Raiden, IPFS, Swarm and Vipnode as well as initial support for Eth2.0 clients.

Images take care of all necessary steps, from setting up the environment to running the Ethereum software and synchronizing the blockchain. All you need is to flash the MicroSD card with the image, plug an ethernet cable and power on the device.

These are the main Ethereum on ARM64 features:

Software installed (image)

Run the following command to update to last versions available

sudo update-ethereum

Ethereum 1.0 clients

Ethereum 2.0 clients

What you need

  1. A Friendly Elec NanoPC-T4 ARM SoC [1] or a RockPro64 ARM SoC [2]
  2. Micro SD Card and SD Adaptor (for flashing the MicroSD)
  3. NVMe M.2 SSD (minimum 256GB, 500GB recommended). Keep in mind that without a NVMe M.2 SSD drive there’s absolutely no chance of syncing the blockchain.
  4. An ethernet cable
  5. EthArmbian image, download link below (see build instructions if you don't own a NanoPC-T4)
  6. (Optional) 30303 Port forwarding. This is a recommended setting (see below)
  7. (Optional) USB keyboard, Monitor and HDMI cable

Ethereum on ARM64 Images

Current packages version: 2020/10/24

Ethereum 2.0 clients

Run "update-ethereum" command to update to the latest versions. This is now an apt-get install alias

Current image release date: 2020/10/24

There are 2 images available. One for the Nanopc-T4 ARM Soc, and one for RockPro64 with Geth as default client:

NANOPC-T4 IMAGE

https://ethraspbian.com/downloads/Armbian_20.11.0-trunk_Nanopct4_focal_legacy_4.4.213.img.zip

SHA256 e1af32421372ed00efa8d4404ba5edf87eae3ba91bf51104ae07bfdf7aedd17e

Install instructions

In a nutshell

  1. Flash the Armbian Image on your MicroSD Card (in your desktop or laptop computer, see below for detailed instructions)
  2. Get the NanoPC-T4 or the RockPro64
  3. Plug in the MicroSD card
  4. Plug in the NVMe M.2 SSD drive
  5. Plug in the Ethernet cable
  6. Power on the board

You are all set. Take into account that the installer needs to perform some operations before it wakes up so you may need to wait about 1 minute (this includes 1 reboot).

For a full Ethereum node to be online the whole blockchain needs to be synced (to the very last block) so it will take some time to get there (see the FAQ section).

Flashing the Ethereum on ARM64 image

MicroSD Install instructions for Linux

Insert the MicroSD in your SD adapter and plug it into your desktop or laptop computer. It is recommended to umount partitions in case you have a preformated card.

Note: If you are not comfortable with command line, you can use Etcher:

https://etcher.io/

  1. Open a terminal and check your MicroSD device name running:

sudo fdisk -l

You should see a device named mmcblk0 or sdd (that matchs with the size of your card. This is a dangerous operation so be careful). For further info please visit:

https://www.raspberrypi.org/documentation/installation/installing-images/linux.md

  1. Flash the MicroSD:

Installing image:

unzip Armbian_20.11.0-trunk_Nanopct4_focal_legacy_4.4.213.img.zip
sudo dd bs=1M if=Armbian_20.11.0-trunk_Nanopct4_focal_legacy_4.4.213.img of=/dev/mmcblk0 && sync
  1. Extract the MicroSD card

You are done. Insert the MicroSD into your ARM SoC and power it on.

Instructions for Windows

Please see:

https://www.raspberrypi.org/documentation/installation/installing-images/windows.md

Instructions for Mac

Please see:

https://www.raspberrypi.org/documentation/installation/installing-images/mac.md

Port forwarding

If you are going to run a full Ethereum node you may forward the 30303 port from your router to your device. This is an optional but recommended setting. There are 2 ways of doing this:

Switching clients

Both clients (Geth and Parity) are included in the image so you can switch from one to another anytime. Let’s say you are running parity, by typing:

sudo systemctl stop parity && sudo systemctl disable parity
sudo systemctl enable geth && sudo systemctl start geth

these commands will disable parity and start the geth daemon.

Managing the daemon

Starting, stopping and getting the client status

Geth and Parity run as a bootup service so the client wakes up automatically. You can stop, start, restart and check the console output using systemctl:

sudo systemctl stop|start|restart|status geth or sudo systemctl stop|start|restart|status parity

Changing settings

Both clients settings are stored on /etc/ethereum/ directory (geth.conf file for geth and parity.conf file for parity), so you just have to edit these files and restart the daemon, for instance, changing cache value in geth:

FAQ

These are some common asked questions:

How do I connect to the board?

You can use SSH or a Monitor + USB keyboard. If you don't have a monitor connected you can discover the Nano IP by connecting to your router or using tools like nmap in order to connect though SSH.

How can I log in?

User: ethereum 
Password: ethereum

It is strongly recommended to change the default password by running:

passwd

You can access as root as well:

User: root
Password: 1234 (you will be prompted to change the default password the first time you log in)

How long does it take to sync the Ethereum blockchain?

For Parity client, just a few hours (4-5). Geth takes 2 and a half days. (as of September 2018).

Which is the blockchain size once synced?

For Parity, 180 GB. For Geth, about 160GB. (as of July 2019). Please note that there is currently an issue with Geth 1.9

I'm seeing lots of "Database compacting, degraded performance" messages (geth)

You are fine. This is an expected behaviour in LevelDB databases. See:

https://github.com/ethereum/go-ethereum/issues/16871#issuecomment-395372313

I'm seeing lots of "Imported new state entries" messages, is the node synced? (geth)

No, not yet. You will need to wait for the whole import process to finish (as of September 2018, about 218 million state entries). More info:

Karalabe Geth syncing explanation

The snapshot synchronization is stuck (parity).

The most probably reason is that the snapshot is no longer available (it changes from time to time). Just stop parity, remove the data and restart the sync process by running:

sudo systemctl stop parity
sudo rm -rf /home/ethereum/.local/share/io.parity.ethereum/
sudo systemctl start parity

Time is not accurate or the Time Zone is incorrect

Run the following command to sync time and change the Time Zone

sudo armbian-config

Go to "Personal" --> "Time zone" and choose the correct one.

Is it possible to sync the blockchain with a SD card or a HDD drive?

Absolutely not. You will need an NVMe M.2 SSD Drive.

Which client is better?

Both clients are great. If you want to keep the blockchain size as low as possible and sync ASAP, Parity is probably the best option. If you want to support light clients or test swarm, you may go for Geth.

Where can I find more info about the blockchain synchronization?

These links are a good start:

Where can I see Geth or Parity logs?

By running one of these commands (depends on the client):

systemctl status geth
systemctl status parity

Also, by running:

tail -f /var/log/syslog

You can also monitor a tail of the log of any service running in the background like so:

sudo journalctl -u geth -f

Can I buy a board with the image preinstalled?

Yes, see the links section. This is ran by Bruno Skvorc and the store is non-profit

Links

Armbian image build instructions (for other devices)

If you don't own a Nanopc-T4 you can build an Armbian custom image for your board (in case is powerfull enough to sync the blockchain). Check here if your device is supported:

https://www.armbian.com/download/

Prerequisites

I strongly recommend the vagrant environment.

Git branch and instructions

For building your own image, please check the Armbian documentation.

https://docs.armbian.com/

Tip

If you want to support EthArmbian you can drop some Ether here :-)

0x10BE809ad5F8Da1C675A26344E05cD9b56De6306